You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
- [ ] Some Page (@exampleusername) #12345
When PRs are merged, make sure to mark that page as completed like this:
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
Tutorial: Tic Tac Toe
Thinking in React
Installation
Start a New React Project
Add React to an Existing Project
Editor Setup
React Developer Tools
Describing the UI
Your First Component
Importing and Exporting Components
Writing Markup with JSX
JavaScript in JSX with Curly Braces
Passing Props to a Component
Conditional Rendering
Rendering Lists
Keeping Components Pure
Adding Interactivity
Responding to Events
State: A Component's Memory
Render and Commit
State as a Snapshot
Queueing a Series of State Updates
Updating Objects in State
Updating Arrays in State
Managing State
Reacting to Input with State
Choosing the State Structure
Sharing State Between Components
Preserving and Resetting State
Extracting State Logic into a Reducer
Passing Data Deeply with Context
Scaling Up with Reducer and Context
Escape Hatches
Referencing Values with Refs
Manipulating the DOM with Refs
Synchronizing with Effects
You Might Not Need an Effect
Lifecycle of Reactive Effects
Separating Events from Effects
Removing Effect Dependencies
Reusing Logic with Custom Hooks
API Reference
react: Hooks
useCallback
useContext
useDebugValue
useDeferredValue
useEffect
useId
useImperativeHandle
useInsertionEffect
useLayoutEffect
useMemo
useReducer
useRef
useState
useSyncExternalStore
useTransition
react: Components
<Fragment> (<>)
<Profiler>
<StrictMode>
<Suspense>
react: APIs
createContext
forwardRef
lazy
memo
startTransition
react-dom: Components
Common (e.g. <div>)
<input>
<option>
<progress>
<select>
<textarea>
react-dom: APIs
createPortal
flushSync
findDOMNode
hydrate
render
unmountComponentAtNode
react-dom/client: Client APIs
createRoot
hydrateRoot
react-dom/server: Server APIs
renderToNodeStream
renderToPipeableStream
renderToReadableStream
renderToStaticMarkup
renderToStaticNodeStream
renderToString
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.
Homepage (currently in HomeContent.js)
Sidebars (currently in src/sidebar*.json)
Top-level navigation (currently in TopNav.tsx)
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:
Legacy React APIs
Children
cloneElement
Component
createElement
createFactory
createRef
isValidElement
PureComponent
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:
If you want to become a maintainer, ask them to add you. If the original maintainers are no longer responsive, raise an issue in the main translations repository.
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. Take only one page at a time.
Check out prior works in Prior works #4 before you get started.
Clone this repo, translate your page using with this checker, and submit a pull request!
Before contributing, read the glossary and this wiki page 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 any more, let the maintainers know so they can assign the page to someone else.
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.
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 like this:
This ensures your translation's progress is tracked correctly at https://translations.react.dev/.
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
Installation
Describing the UI
Adding Interactivity
Managing State
Escape Hatches
API Reference
react: HooksuseCallbackuseContextuseDebugValueuseDeferredValueuseEffectuseIduseImperativeHandleuseInsertionEffectuseLayoutEffectuseMemouseReduceruseRefuseStateuseSyncExternalStoreuseTransitionreact: Components<Fragment> (<>)<Profiler><StrictMode><Suspense>react: APIscreateContextforwardReflazymemostartTransitionreact-dom: Components<div>)<input><option><progress><select><textarea>react-dom: APIscreatePortalflushSyncfindDOMNodehydraterenderunmountComponentAtNodereact-dom/client: Client APIscreateRoothydrateRootreact-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:
Maintainer List
This translation is maintained by:
If you want to become a maintainer, ask them to add you. If the original maintainers are no longer responsive, raise an issue in the main translations repository.
Click here to see reactjs.org legacy progress
Maintainer List
For New Translators
To translate a page:
Before contributing, read the glossary and this wiki page 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 any more, let the maintainers know so they can assign the page to someone else.
Please join in React Korea Slack #translation channel if you are interested in the translation.
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!
Core Pages
To do before releasing as an "official" translation. Please translate these pages first.
Basics
API Reference
Navigation
These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.
Next Steps
These are the next most important translations, ordered by importance:
Installation
Hooks
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.
Warnings
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.
Advanced Guides
@gnujoow@dev-hikun)higher-order-components (partial) #187Translated HOC Page #286FAQ
Contributing
Priority: Low
Components
Components in
src/componentsthat have some text in them.Additional Translations
These are not the primary translation targets.
Translations added after this issue creation
Testing
Concurrent Mode (Experimental)