Maintainer List
For New Translators
To translate a page:
- Check that no one else has claimed your page in the checklist and comments below.
- Comment below with the name of the page you would like to translate. Please take only one page at a time.
- Clone this repo, translate your page, and submit a pull request!
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
- [ ] Quick Start (@tesseralis) #12345
When PRs are merged, make sure to mark that page as completed!
Main Content
To do before releasing as an "official" translation. Please translate these pages first.
Note that each section has an index page, which needs to be translated too.
Learn React
API Reference
Navigation and UI
We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.
When You're Ready...
After everything above is translated, add your language to deployedLanguages in Seo.tsx of the original reactjs/react.dev repository.
Secondary Content
These API pages should ideally be translated too, but they're less urgent and can be done after the others:
Optional Content
These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages:
Maintainer List
For New Translators
To translate a page:
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
Main Content
To do before releasing as an "official" translation. Please translate these pages first.
Note that each section has an index page, which needs to be translated too.
Learn React
Quick Start (@Yarob50) [DONE]: Translating "Quick Start / Index Page" #465
Installation (@AbdulrehmanSuliman) [DONE]: Translation of Installation #475
Add React to an existing project#473Editor-Setup.md#479React Developer tools#476Describing the UI (@algorizr ) [DONE]: Translate
Describing the UIpage #472Your First Component#488Importing and Exporting Compoenents#481Writing-markup-with-jsx.md#480JavaScript in JSX with Curly Braces#498Adding Interactivity (@abdllahdev) [DONE]: Translate
Adding Interactivity#516Render and Commit#478Managing State (@Rumbustious) Translate
Managing Statepage #522Escape Hatches
API Reference
Overview
react: Hooks (@aalhommada) translate reference react index page #477useuseCallbackuseContextuseDebugValue(@remahmoud) [Done] TranslatinguseDebugValue#489useDeferredValueuseEffectuseId(@remahmoud) useId page translation #483useImperativeHandleuseInsertionEffectuseLayoutEffectuseMemouseOptimisticuseReduceruseRefuseState(@r-m169)useSyncExternalStoreuseTransitionreact: Components (@AhmedBaset) Translating Reference: React/Components #509<Fragment> (<>)<Profiler><StrictMode><Suspense>react: APIs (@AhmedBaset) Translating: APIs index page #507createContextcacheforwardReflazymemostartTransitionactRSC
'use client'and'use server'. #505"use client""use server"(@AhmedBaset) Translating directives,'use client'and'use server'. #505experimental_taintObjectReferenceexperimental_taintUniqueValueRules
Hooks
useFormStateuseFormStatusreact-dom: Components<div>)<form><input><option>(@muh-osman) Translate<option>page [UPDATED] #487<progress>(@mrlahmar) [DONE] translate <progress> page #491<select><textarea><script><meta><link><style><title>react-dom: APIs (@AhmedBaset) Translating: Reference/react-dom/index #508createPortalflushSyncfindDOMNodehydratepreconnectprefetchDNSpreinitpreinitModulepreloadpreloadModulerenderunmountComponentAtNodereact-dom/client: Client APIs (@AhmedBaset) Translating: Client section in the react-dom reference #510createRoot(@AhmedBaset) Translating: Client section in the react-dom reference #510hydrateRootreact-dom/server: Server APIsrenderToNodeStreamrenderToPipeableStreamrenderToReadableStreamrenderToStaticMarkuprenderToStaticNodeStreamrenderToStringNavigation and UI
We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.
HomeContent.js)src/sidebar*.json)TopNav.tsx)When You're Ready...
After everything above is translated, add your language to
deployedLanguagesinSeo.tsxof the original reactjs/react.dev repository.Secondary Content
These API pages should ideally be translated too, but they're less urgent and can be done after the others:
ChildrencloneElementComponentcreateElementcreateFactorycreateRefisValidElementPureComponentOptional Content
These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages: