Description
New Site Translation Progress
Maintainer List
Retired maintainers
Preview
Original issue
This issue was based on: reactjs/react.dev#4135
How to translate
If you want to help with translation, please leave a comment in this issue and write the name of the page you would like to translate. One of the repo maintainers will add your GitHub nickname next to the page to "make a reservation".
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 (@jakubdrozdek) Translate Quick start page #335
- Tutorial: Tic Tac Toe
- Thinking in React (@jakubdrozdek) Translate Thinking in React page #333
-
Installation
- Start a New React Project (@dawidsabat) Translate Start a new react project page #444
- Add React to an Existing Project (@tomaszwysocki) Translate Add React to an Existing Project page #454
- Editor Setup (@jakubdrozdek) Translate Editor setup page #291
- React Developer Tools (@jakubdrozdek) Translate React Developer Tools page #292
-
Describing the UI (@jakubdrozdek) Translate Describing the UI page #340
- Your First Component (@jakubdrozdek) Translate Your first component #294
- Importing and Exporting Components (@jakubdrozdek) Translate Importing and exporting components page #295
- Writing Markup with JSX (@jakubdrozdek) Translate Writing markup with JSX page #298
- JavaScript in JSX with Curly Braces (@jakubdrozdek) Translate JavaScript in JSX with curly braces #300
- Passing Props to a Component (@jakubdrozdek) Translate Passing props to a component page #301
- Conditional Rendering (@lukbar48) Translated Conditional Rendering article #302
- Rendering Lists (@dawidsabat) Translate Rendering Lists page #460
- Keeping Components Pure (@dawidsabat) Translate Keeping components pure #464
-
Adding Interactivity (@dawidsabat) Translate Learn / Adding interactivity #478
- Responding to Events (@wizarddos) "Responding to events" translation #491
- State: A Component's Memory (@Rohhan415) Translation of state a components memory #510
- Render and Commit (@dawidsabat) Translate Render and commit #465
- State as a Snapshot (@dawidsabat) Learn / State as a Snapshot #494
- Queueing a Series of State Updates (@Rohhan415)
- 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 (@dawidsabat) Learn / Preserving and resetting state #490
- Extracting State Logic into a Reducer
- Passing Data Deeply with Context
- Scaling Up with Reducer and Context
-
Escape Hatches
- Referencing Values with Refs (@piotr-pajak) Learn / Referencing Values with Refs #511
- Manipulating the DOM with Refs (@piotr-pajak)
- 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
(@dawidsabat) Translation of useCallback reference #423 -
useContext
-
useDebugValue
-
useDeferredValue
-
useEffect
(@dawidsabat) useEffect reference #431 -
useId
-
useImperativeHandle
-
useInsertionEffect
-
useLayoutEffect
-
useMemo
-
useReducer
-
useRef
-
useState
(@jakubdrozdek) Translate useState hook API #341 -
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>
- Common (e.g.
-
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:
- Community
- Blog
- Warnings