New Translation Progress Checklist

ページを翻訳したい方へ：

重複作業を防ぐため、まずはここでどのページを翻訳するか宣言してください。宣言なしで翻訳が行われて他の人の作業と被ってしまった場合、原則として（PRを先に作った人ではなく）ここで最初に宣言があった人を優先します。ただし宣言が行われて 1 週間以上 PR が作成されないなどの場合は適宜対応します。

スタイルガイドおよび単語リストをチェックして、翻訳が一貫した方法で書かれていることを確認してください。

New Articles

Progress : (🏃 進行中の作業; 👀 レビュー中）

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 (@smikitky #559)

  • Tutorial: Tic Tac Toe (@smikitky #562)
  • Thinking in React (@smikitky #560)

• Installation (@smikitky, #555)

  • Start a New React Project (@smikitky, #555)
  • Add React to an Existing Project (@smikitky, #555)
  • Editor Setup (@smikitky, #555)
  • Using TypeScript (@smikitky, #659)
  • React Developer Tools (@smikitky, #555)

• Describing the UI (@smikitky #556)

  • Your First Component (@smikitky, #451)
  • Importing and Exporting Components (@smikitky, #451)
  • Writing Markup with JSX (@smikitky #459)
  • JavaScript in JSX with Curly Braces (@smikitky #459)
  • Passing Props to a Component (@smikitky #461)
  • Conditional Rendering (@smikitky #556)
  • Rendering Lists (@smikitky #556)
  • Keeping Components Pure (@smikitky #556)
  • Understanding Your UI as a Tree (@smikitky, #706)

• Adding Interactivity (@pasteisdenata, #491)

  • Responding to Events (@smikitky, #567)
  • State: A Component's Memory (@smikitky, #567)
  • Render and Commit (@smikitky, #567)
  • State as a Snapshot (@smikitky, #569)
  • Queueing a Series of State Updates (@smikitky, #569)
  • Updating Objects in State (@smikitky, #574)
  • Updating Arrays in State (@smikitky, #574)

• Managing State (@smikitky, #610)

  • Reacting to Input with State (@youliangdao, #571)
  • Choosing the State Structure (@smikitky, #588)
  • Sharing State Between Components (@smikitky, #582)
  • Preserving and Resetting State (@smikitky, #583)
  • Extracting State Logic into a Reducer (@smikitky, #584)
  • Passing Data Deeply with Context (@smikitky, #586)
  • Scaling Up with Reducer and Context (@smikitky, #587)

• Escape Hatches (@smikitky, #620)

  • Referencing Values with Refs (@smikitky, #590)
  • Manipulating the DOM with Refs (@smikitky, #589)
  • Synchronizing with Effects (@smikitky, #594)
  • You Might Not Need an Effect (@smikitky, #604)
  • Lifecycle of Reactive Effects (@yuta-ike, #601)
  • Separating Events from Effects (@kotaesaki, #609)
  • Removing Effect Dependencies (@smikitky, #611)
  • Reusing Logic with Custom Hooks (@smikitky, #605)

API Reference

• react: Hooks (@Hayao0819, #618)

  • use (@smikitky, #687)
  • useCallback (@seckie, #591)
  • useContext (@jp-knj, #621)
  • useDebugValue (@seckie, #573)
  • useDeferredValue (@smikitky, #622)
  • useEffect (@smikitky, #568)
  • useId (@sbasken, #608)
  • useImperativeHandle (@sbasken, #614)
  • useInsertionEffect (@smikitky, #625)
  • useLayoutEffect (@smikitky, #624)
  • useMemo (@yuta-ike, #643)
  • useOptimistic (@smikitky, #717)
  • useReducer (@locol23, #641)
  • useRef (@yuta-ike, #613)
  • useState (@yuta-ike, #595)
  • useSyncExternalStore (@jp-knj, #619)
  • useTransition (@smikitky, #623)

• react: Components (@smikitky, #686)

  • <Fragment> (<>) (@jp-knj, #626)
  • <Profiler> (@smikitky, #629)
  • <StrictMode> (@smikitky, #630)
  • <Suspense> (@smikitky, #628)

• react: APIs (@natsuokawai, #636)

  • cache (@locol23, #696)
  • createContext (@natsuokawai, #638)
  • forwardRef (@smikitky, #631)
  • lazy (@smikitky, #633)
  • memo (@smikitky, #702)
  • startTransition (@smikitky, #623)

• react: Directives (@smikitky, #635)

  • 'use client' (@smikitky, #635)
  • 'use server' (@smikitky, #635)

• react-dom: Components (@smikitky, #682)

  • Common (e.g. <div>) (@smikitky, #637)
  • <input> (@sbasken, #646)
  • <form> (@smikitky, #715)
  • <option> (@smikitky, #678)
  • <progress> (@natsuokawai, #640)
  • <select> (@ainoshment, #644)
  • <textarea> (@smikitky, #649)

• react-dom: Hooks (@smikitky, #723)

  • useFormState (@smikitky, #722)
  • useFormStatus (@smikitky, #721)

• react-dom: APIs (@smikitky, #681)

  • createPortal (@smikitky, #647)
  • flushSync (@smikitky, #650)
  • findDOMNode (@jp-knj, #670)
  • hydrate (@riku929hr, #653)
  • render (@smikitky, #663)
  • unmountComponentAtNode (@smikitky, #660)

• react-dom/client: Client APIs (@smikitky, #662)

  • createRoot (@smikitky, #661)
  • hydrateRoot (@smikitky, #669)

• react-dom/server: Server APIs (@smikitky, #656)

  • renderToNodeStream (@smikitky, #655)
  • renderToPipeableStream (@smikitky, #654)
  • renderToReadableStream (@smikitky, #654)
  • renderToStaticMarkup (@smikitky, #655)
  • renderToStaticNodeStream (@smikitky, #655)
  • renderToString (@smikitky, #655)

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) (@smikitky, #570)
• Sidebars (currently in src/sidebar*.json) (@smikitky, #658)
• 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 (@smikitky, #693)
  • Children (@smikitky, #684)
  • cloneElement (@smikitky, #685)
  • Component (@smikitky, #677)
  • createElement (@smikitky, #688)
  • createFactory (@smikitky, #690)
  • createRef (@smikitky, #689)
  • isValidElement (@smikitky, #691)
  • PureComponent (@smikitky, #692)

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 (@smikitky, #668)
• Blog
• Warnings

Start by checking the unchecked Warnings entry and the linked style guide and terminology list. The payload names source/layout files such as HomeContent.js, src/sidebar*.json, TopNav.tsx, and Seo.tsx, but does not identify the Warnings translation file. Done would require a defined target, a Japanese translation following those guides, and updating this checklist with the resulting PR.