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:
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.
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.
The text was updated successfully, but these errors were encountered:
Hi @gaearon! Most definitely. I've been busy otherwise and haven't yet gotten around to migrating to the new repo yet. The translation work has been underway here: mirorauhala/fi.reactjs.org#1
I'll start to move content from there to here at the end of this month at the latest.
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 (@mirorauhala) 🎉 Move existing translations to new repo #6
Installation (@mirorauhala) 🎉 Move existing translations to new repo #6
Describing the UI (@mirorauhala) 🎉 Move existing translations to new repo #6
Adding Interactivity (@mirorauhala) 🎉 Move existing translations to new repo #6
Managing State (@mirorauhala) 🎉 Move existing translations to new repo #6
Escape Hatches (@mirorauhala) Translate Escape Hatches #27
API Reference
react
: HooksuseCallback
useContext
useDebugValue
useDeferredValue
useEffect
useId
useImperativeHandle
useInsertionEffect
useLayoutEffect
useMemo
useReducer
useRef
useState
useSyncExternalStore
useTransition
react
: Components<Fragment> (<>)
(@mirorauhala) Translate 'Fragment' #49<Profiler>
<StrictMode>
<Suspense>
react
: APIscreateContext
(@mirorauhala) Translate 'createContext' #11forwardRef
(@mirorauhala) Translate 'forwardRef' #12lazy
memo
startTransition
Directives (@mirorauhala) Sync with react.dev @ 2390627c #46
use client
(@mirorauhala) Translate 'use client' #39use server
(@mirorauhala) Translate 'use server' #40react-dom
: Components (@mirorauhala) Translate Components #45<div>
) (@mirorauhala) Translate Components #45<input>
(@mirorauhala) Translate Components #45<option>
(@mirorauhala) Translate Components #45<progress>
(@mirorauhala) Translate Components #45<select>
(@mirorauhala) Translate Components #45<textarea>
(@mirorauhala) Translate Components #45react-dom
: APIscreatePortal
flushSync
findDOMNode
hydrate
render
unmountComponentAtNode
react-dom/client
: Client APIscreateRoot
hydrateRoot
react-dom/server
: Server APIsrenderToNodeStream
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.
HomeContent.js
) (@mirorauhala) 🎉 Move existing translations to new repo #6src/sidebar*.json
) (@mirorauhala) Translate sidebar #28TopNav.tsx
) (@mirorauhala) Translate TopNav #29When You're Ready...
After everything above is translated, add your language to
deployedLanguages
inSeo.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:
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:
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.
The text was updated successfully, but these errors were encountered: