Repository navigation
[Beta] Translating New React Docs #4135
Description
It's time to translate new React docs at https://react.dev!
- Translation status: https://translations.react.dev/
- How to start a new translation: https://github.com/reactjs/translations.react.dev
Who is this issue for?
This issue is for existing translation repo maintainers.
What is ok to translate now?
All pages in src/content are good to translate.
Something unclear?
Please comment here with concerns or suggestions. Originally we wanted to suggest translating when more of the content is written. However, some translators have expressed interest in starting earlier so that's why we made this issue.
Activity
arshadkazmi42 commentedon Nov 29, 2021
Hi @gaearon
Does that mean, we should stop the translation of the current website, which in progress? And start focusing on this?
gaearon commentedon Nov 29, 2021
I think that would make the most sense. (Sorry if you spent a bunch of effort on this.)
arshadkazmi42 commentedon Nov 29, 2021
Thank you for confirmation. Will start working towards that.
jakubdrozdek commentedon Nov 29, 2021
@gaearon Hey, I just started working on the Polish docs, but unfortunately my first PR's CI checks fail on
Analyze bundlejob.https://github.com/reactjs/pl.reactjs.org/runs/4360534093?check_suite_focus=true
Do you know what's the problem? Is it required to pass?
And second question: where can we preview our translated website and what's the URL for the live Polish beta? The link in PR for Vercel app links to the old React docs: https://plreactjsorg-7luo3ndx9-fbopensource.vercel.app/
smikitky commentedon Nov 30, 2021
@jakubdrozdek That happened on our fork (Japanese), too. That dawidd6/action-download-artifact@v2 GitHub action tries to download "external" files (artifact) that had been generated by a workflow executed on the
mainbranch. You got that error because no relevant workflow has been previously merged into themain. If I understand correctly, you can ignore that error and just merge the PR for now. Everything should be fine from the next PR.gaearon commentedon Nov 30, 2021
Like @smikitky said, try without it passing and see if that resolves next time. I wouldn't worry about it for now.
If you write a few pages I'll set up a project. Unfortunately it's manual so write here and we'll do it.
smikitky commentedon Dec 1, 2021
The current pre-commit hook has the following two lines:
https://github.com/reactjs/reactjs.org/blob/4022f9774b8dd93d863fd6bca6447b1f03ae3979/beta/.husky/pre-commit#L5-L6
This may make sense on the main repo but makes no sense on translation forks. Every time I commit, I see many useless notices saying the explicit IDs are different from auto-generated ones.
https://github.com/reactjs/reactjs.org/blob/4022f9774b8dd93d863fd6bca6447b1f03ae3979/beta/scripts/generateHeadingIDs.js#L55-L57
What's worse, because of the unconditional
git add -u, I accidentally committed and pushed a draft translation without knowing it. I think this process could be smarter and less confusing to new translators.gaearon commentedon Dec 1, 2021
@smikitky yeah this sounds confusing! do you have a fix in mind? how did this work before?
hg-pyun commentedon Dec 1, 2021
@gaearon Is there a schedule for the official release of new documents? It would be nice to share roughly.
smikitky commentedon Dec 1, 2021
@gaearon In the future, it would be nice to run pre-commit generate-ids only on the main repo. When it finds a heading without an explicit ID, it should reject the commit instead of unconditionally fixing it and committing it. Alternatively, it could auto-fix only the files to be committed, not all the files in the src directory.
But in the meantime, I think this pre-commit hook could be simply removed.
harish-sethuraman commentedon Dec 1, 2021
We might have to write a custom hook for that will look into that.
Will remove it
jakubdrozdek commentedon Dec 2, 2021
@gaearon Hey, I just finished translating the whole first chapter, and going on. Do you think it's enough to deploy the Polish beta docs now? 😉
reactjs/pl.react.dev#287
smikitky commentedon Dec 4, 2021
@gaearon Please set up the Japanese beta docs, too. Translations for several pages and MDX tags were merged into main.
gaearon commentedon Dec 4, 2021
I actually just went on a vacation but I asked @rickhanlonii to find someone from the team to help with this. Ping me in twitter DM if there’s no progress in a week and I’ll double check.
117 remaining items
Translate README.md (#763)
ysh199882 commentedon Aug 13, 2023
Hello,
I am a loyal user of React. I would like to contribute to the translation of the React documentation. However, I noticed that there used to be a progress indicator for Simplified Chinese translation in this image, but now it's gone. Was there any particular reason for this change?
smikitky commentedon Aug 29, 2023
Hi, I think many translators are still following this issue, so let me introduce this this small tool to translate OGP images stored as
public/images/og-*.png. Such images are used by Facebook and other SNS.https://codesandbox.io/p/sandbox/react-ogp-image-generator-8299gn
You can generate images like this in 30 seconds:
RTL and composite fonts are not supported, but you can edit the source code to suit your needs.
smikitky commentedon Aug 29, 2023
By the way, if there are translators who are wondering why the new translations are not showing up on Google, please refer to #6260.
tdd commentedon Aug 30, 2023
Thank you for this! Just used it for the FR translation 😉
fabiarias commentedon Sep 17, 2024
I would like to help with the translate.
MiryamMann commentedon Apr 19, 2025
Is there a translation in Hebrew already?
I'll be happy to translate articles in React web to Hebrew.
Please let me know if I can begin.
Ni-zav commentedon May 11, 2025
I am starting to contribute to this react.dev, may I know is it okay to translate the title in the frontmatter?
smartcoder0777 commentedon Jan 8, 2026
Hi @gaearon,
It looks like there isn't a translation in Spanish.
If you need it, I can work on it.
Looking forward to hearing from you.
Thanks,
Pavel
tdd commentedon Jan 8, 2026
Hey @smartcoder0777.
Not sure what gave you that idea. ES has been one of the first langs to reach completion.
https://es.react.dev/ • https://github.com/reactjs/es.react.dev
Not sure why it doesn't show up on translations.react.dev anymore, though, but judging by their open PRs they're pretty up-to-date.
smartcoder0777 commentedon Jan 8, 2026
Hi @tdd ,
Thanks for your response.
By the way I'd like to take part in contributing on React.dev.
I saw that there are many issues with different tags.
Would you like to let me know which tag has a priority or good for new comers?
Best,
Pavel
tdd commentedon Jan 8, 2026
Hey @smartcoder0777! I'm actually not involved these days in the translations anymore… FR used to be best-of-breed and is now lagging almost a year behind.
I'm not the proper contact point when it comes to contributing to the upstream repo or some other translation, but do feel free to simply write PRs to address outstanding tickets, especially if such issues were acknowledged by the docs team.
smartcoder0777 commentedon Jan 8, 2026
Hi @tdd ,
You look like misunderstood me. I can translate documentations in several languages but I am a developer with experiences in React and Node.js.
So, I'd like to contribute to your repository but as you know, there are so many issues with many labels.
I am not sure, which one is good for me to start. So, if you can guide me once, I will appreciate it.
Thanks,
Pavel
tdd commentedon Jan 8, 2026
Hey @smartcoder0777! Sorry about the misunderstanding.
This link filters this repo's issues on open issues less than 3 years old (so they don't pertain to legacy docs) that are either typos or "good first issue" stuff.
That's a good springboard for contributing. Now, some of these typos may well not exist anymore (core team's docs updates rarely if ever look at issues their updates might be closing), so do double-check, but that should help sift stuff down.
I also don't think legacy docs issues should remain open, but before anyone goes on mass-closing them, perhaps getting approval from a core docs team member would be best!