Korean Translation Progress

[tesseralis]

trafficstars

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate. Please take only one page at a time.
3. 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:

- [x] Some Page (@exampleusername) #12345

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

• [x] Quick Start

  • [x] Tutorial: Tic Tac Toe
  • [x] Thinking in React

• [x] Installation

  • [x] Start a New React Project
  • [x] Add React to an Existing Project
  • [x] Editor Setup
  • [x] React Developer Tools

• [x] Describing the UI

  • [x] Your First Component
  • [x] Importing and Exporting Components
  • [x] Writing Markup with JSX
  • [x] JavaScript in JSX with Curly Braces
  • [x] Passing Props to a Component
  • [x] Conditional Rendering
  • [x] Rendering Lists
  • [x] Keeping Components Pure

• [x] Adding Interactivity

  • [x] Responding to Events
  • [x] State: A Component's Memory
  • [x] Render and Commit
  • [x] State as a Snapshot
  • [x] Queueing a Series of State Updates
  • [x] Updating Objects in State
  • [x] Updating Arrays in State

• [x] Managing State

  • [x] Reacting to Input with State
  • [x] Choosing the State Structure
  • [x] Sharing State Between Components
  • [x] Preserving and Resetting State
  • [x] Extracting State Logic into a Reducer
  • [x] Passing Data Deeply with Context
  • [x] Scaling Up with Reducer and Context

• [x] Escape Hatches

  • [x] Referencing Values with Refs
  • [x] Manipulating the DOM with Refs
  • [x] Synchronizing with Effects
  • [x] You Might Not Need an Effect
  • [x] Lifecycle of Reactive Effects
  • [x] Separating Events from Effects
  • [x] Removing Effect Dependencies
  • [x] Reusing Logic with Custom Hooks

API Reference

• [x] react: Hooks

  • [x] useCallback
  • [x] useContext
  • [x] useDebugValue
  • [x] useDeferredValue
  • [x] useEffect
  • [x] useId
  • [x] useImperativeHandle
  • [x] useInsertionEffect
  • [x] useLayoutEffect
  • [x] useMemo
  • [x] useReducer
  • [x] useRef
  • [x] useState
  • [x] useSyncExternalStore
  • [x] useTransition

• [x] react: Components

  • [x] <Fragment> (<>)
  • [x] <Profiler>
  • [x] <StrictMode>
  • [x] <Suspense>

• [x] react: APIs

  • [x] createContext
  • [x] forwardRef
  • [x] lazy
  • [x] memo
  • [x] startTransition

• [x] react-dom: Components

  • [x] Common (e.g. <div>)
  • [x] <input>
  • [x] <option>
  • [x] <progress>
  • [x] <select>
  • [x] <textarea>

• [x] react-dom: APIs

  • [x] createPortal
  • [x] flushSync
  • [x] findDOMNode
  • [x] hydrate
  • [x] render
  • [x] unmountComponentAtNode

• [x] react-dom/client: Client APIs

  • [x] createRoot
  • [x] hydrateRoot

• [x] react-dom/server: Server APIs

  • [x] renderToNodeStream
  • [x] renderToPipeableStream
  • [x] renderToReadableStream
  • [x] renderToStaticMarkup
  • [x] renderToStaticNodeStream
  • [x] 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.

• [x] Homepage (currently in HomeContent.js)
• [x] Sidebars (currently in src/sidebar*.json)
• [x] 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:

• [x] Legacy React APIs
  • [x] Children
  • [x] cloneElement
  • [x] Component
  • [x] createElement
  • [x] createFactory
  • [x] createRef
  • [x] isValidElement
  • [x] 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:

• [x] Community
• [x] Blog
• [x] Warnings

Maintainer List

This translation is maintained by:

• @hg-pyun
• @taehwanno
• @simsim0709
• @gnujoow
• @b9words
• @taggon
• @MaxKim-J
• @eomttt
• @lumirlumir

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

• @taehwanno
• @simsim0709
• @hg-pyun
• @gnujoow
• @b9words
• @taggon

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate. Take only one page at a time.
3. Check out prior works in #4 before you get started.
4. 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.

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:

• [ ] Home Page (@tesseralis) #1

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.

• [x] Home Page (@chatoo2412) #8
• [x] Tutorial (@noahluftyang) #111

Basics

• [x] Hello World (@chayeoi) #9
• [x] Introducing JSX (@rkdmen) #18
• [x] Rendering Elements (@BKJang) #21
• [x] Components and Props (@purelledhand) #35
• [x] State and Lifecycle (@rlagksruf16) #95
• [x] Handling Events (@Godsenal) #19
• [x] Conditional Rendering (@Jonir227) #26
• [x] Lists and Keys (@Jravvit) #85
• [x] Forms (@hyunalee419) #30
• [x] Lifting State Up (@chayeoi) #109
• [x] Composition vs Inheritance (@hewonjeong) #22
• [x] Thinking in React (@yesjin-git) #77

API Reference

• [x] React (@cadenzah) #12
• [x] React.Component (@cadenzah) #76
• [x] ReactDOM (@noahluftyang) #28
• [x] ReactDOMServer (@Injae-Lee) #68
• [x] DOM Elements (@stepover10) #67
• [x] SyntheticEvent (@Beingbook) #32
• [x] Test Utilities (@ymin1103) #43
• [x] Shallow Renderer (@hmu332233) #40
• [x] Test Renderer (@hiddenest, @toy9910) #37, #190
• [x] JS Environment Requirements (@taggon) #34
• [x] Glossary (@gnujoow) #16

Navigation

These are the navigation links that appears in the sidebar. Possibly wait until the corresponding sections are translated to do these.

• [x] tutorial/nav.yml (@taehwanno) #87
• [x] docs/nav.yml (@taehwanno, @rkdmf1026) #84, #189

Next Steps

These are the next most important translations, ordered by importance:

Installation

• [x] Getting Started (@MDJuniooor) #50
• [x] Add React to a Website (@ymin1103) #101
• [x] Create a New React App (@OnesQuared) #64
• [x] CDN Links (@gnujoow) #44
• [x] Release Channels (@thinkanddoit) #269

Hooks

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

• [x] Introducing Hooks (@Geon-wooBryanKim) #33
• [x] Hooks at a Glance (@chatoo2412) #6
• [x] Using the State Hook (@nghy97) #65
• [x] Using the Effect Hook (@yumidev) #205
• [x] Rules of Hooks (@BeomyeonAndrewKim) #63
• [x] Building Your Own Hooks (@yumidev) #230
• [x] Hooks API Reference (@hapumee) #89
• [x] Hooks FAQ (@seanjun21) #265

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.

• [x] dont-call-proptypes (@simsim0709) #52
• [x] invalid-aria-prop (@simsim0709) #57
• [x] invalid-hook-call-warning (@simsim0709) #61
• [x] legacy-factories (@simsim0709) #58
• [x] refs-must-have-owner (@simsim0709) #69
• [x] special-props (@simsim0709) #59
• [x] unknown-prop (@simsim0709) #70

Advanced Guides

• [x] Accessibility (@hiddenest) #46
• [x] Code-Splitting (@liante0904) #55
• [x] Context (@phoebejhhong) #79
• [x] Error Boundaries (@anthonyminyungi) #222
• [x] Forwarding Refs (@hapumee) #260
• [x] Fragments (@yoeubi) #83
• [x] Higher-Order Components (~@gnujoow~ @dev-hikun) ~#187~ #286
• [x] Integrating with Other Libraries (@yoeubi) #121
• [x] JSX In Depth (@hIkipooh) #100, #177
• [x] Optimizing Performance (@BeomyeonAndrewKim) #119
• [x] Portals (@hapumee) #131
• [x] Profiler (@hIkipooh) #238
• [x] React Without ES6 (@ymin1103) #29
• [x] React Without JSX (@shiincs) #86
• [x] Reconciliation (@hewonjeong) #60
• [x] Refs and the DOM (@ENvironmentSet) #13
• [x] Render Props (@hg-pyun) #73
• [x] Static Type Checking (@jiwonkirn) #88
• [x] Strict Mode (@hiddenest) #47
• [x] Typechecking With PropTypes (@sukjae) #78
• [x] Uncontrolled Components (@hyunalee419) #66
• [x] Web Components (@hiddenest) #48

FAQ

• [x] APIs and AJAX (@sukjae) #80
• [x] Babel, JSX, and Build Steps (@sukjae) #81
• [x] Passing Functions to Components (@sdu6342) #105
• [x] Component State (@ejolie) #102
• [x] Styling and CSS (@sukjae) #223
• [x] File Structure (@highspirit7) #107
• [x] Versioning Policy (@hapumee) #132
• [x] Virtual DOM and Internals (@dl0312) #113

Contributing

Priority: Low

• [x] How to Contribute (@Kim-Ki-Soo) #126
• [x] Codebase Overview (@Kimguyeop) #123
• [x] Implementation Notes (@baekjuwon) #129
• [x] Design Principles (@hapumee) #133

Components

Components in src/components that have some text in them.

• [x] CodeEditor (@taggon) #361
• [x] CodeExample (@taggon) #361
• [x] ErrorDecoder (@hikipooh) #219
• [x] LayoutFooter (@hoony2520) #122
• [x] LayoutHeader (@AlexKoala) #56
• [ ] MarkdownPage (@dexterastin)

Additional Translations

These are not the primary translation targets.

• [ ] Blog
• [ ] Community

Translations added after this issue creation

Testing

• [x] Testing Overview (@koDaegon) #179
• [x] Testing Recipes (@cdsleaf) #201
• [x] Testing Environments (@BeomYoung) #183

Concurrent Mode (Experimental)

• [x] Introducing Concurrent Mode (@Yohan-Kim2) #186
• [x] Suspense for Data Fetching (@cadenzah) #221
• [x] Concurrent UI Patterns (@Beingbook) #224
• [x] Adopting Concurrent Mode (@junsikshim) #182
• [x] Concurrent Mode API Reference (@DDOLDDOL) #192

[taehwanno]

@tesseralis Hi. Thanks for kind explanation. Can you change the glossary link in issue description to this reactjs.org link? This link may change if a style guide for Korean translation is created.

[taehwanno]

For new translators :runner:, Please first check out #4

[tesseralis]

@taehwanno you should be able to edit the issue directly! Just click the ellipsis > "Edit"

[taehwanno]

@tesseralis I tried, but I do not seem to have the authority :)

[tesseralis]

Ah! Sorry, I thought you were already one of the maintainers. I can add you to the list! You've done a lot of good work already finding all those resources!

[taehwanno]

@tesseralis Sweet, Thanks.

[seungha-kim]

@tesseralis I am a contributor of React Crowdin project, but there is no progression for a long time at all. Is really able to work in crowdin project? And what's your plan for merging PRs & Crowdin translations?

[tesseralis]

Hi @seungha-kim .

Please see the original issue here: https://github.com/reactjs/reactjs.org/issues/1605

Long story short, we decided that doing the translations directly on Github was the better approach since:

• Developers are more likely to understand git version control
• People are interested in contributing to the React repo

As for integrating Crowdin, we're encouraging people to use the Crowdin translations as a base. So you can just copy-paste your work from Crowdin, verify that it's up to date, and submit a pull request!

[seungha-kim]

I think there is no motivation to use Crowdin then :( I am likely to do job once using Git, rather than twice.

[chatoo2412]

~I have a translation of Hooks at a Glance page. I will polish and submit PR.~

PR submitted: #6

[tesseralis]

@chatoo2412 thank you for you PR! In the future, please let us know in a comment here when you're working on a page, so that we don't duplicate work with others. Also, we'd like to focus on the sections listed under "Core Pages"!

[chatoo2412]

@tesseralis I wanted to contribute using my prior work.

~I'll continue with Home Page refer to the prior works.~ PR submitted: #8

[cadenzah]

~~@tesseralis I want to start off with API Reference, beginning with React Top-level API.~~ PR submitted: #12

[tesseralis]

@hg-pyun @simsim0709 @gnujoow , as maintainers, could you keep track of this issue and assign people by editing the issue?

[gnujoow]

@hg-pyun @simsim0709 @gnujoow , as maintainers, could you keep track of this issue and assign people by editing the issue?

I will 👍

[ENvironmentSet]

@gnujoow is this document available to translate? If it is, I want to translate it. can I?

[gnujoow]

@gnujoow is this document available to translate? If it is, I want to translate it. can I?

@ENvironmentSet of course you can! please do 😄

[chayeoi]

I want to work on Hello World.

[simsim0709]

@tesseralis yes, I will. Thanks

[purelledhand]

@gnujoow is this document available to translate? If it is, I want to translate it. can I?

I want to participate in the translation. Could you invite me please? 😊

[ENvironmentSet]

@purelledhand Oh, Did you meant translation of refs-and-the-dom document? or just translation of react document?

[cadenzah]

Following React Top-level API, I will translate the next document, React.Component PR Opened (#76)

[tesseralis]

@cadenzah you got it!

[rkdmen]

@tesseralis I’ll take Introducing JSX

[taehwanno]

@rkdmen Thanks. You got it.

[noahluftyang]

~~If it's available, I wanna translate ReactDOM part.~~ PR submitted: #28

[purelledhand]

@purelledhand Oh, Did you meant translation of refs-and-the-dom document? or just translation of react document?

~~the latter one. @tesseralis I wanna take Components and Props~~ PR submitted: #35

[ENvironmentSet]

@purelledhand then you should ask to maintainer. I'm not a maintainer.

[taehwanno]

@noahluftyang Thanks. You got it.

[taehwanno]

@purelledhand You got it. :rocket: