there are some PR requests with a month long no response from PR author.

For effective project progress and participation of other participants, I suggest to make rule dealing with un-managed reviewed pull requests.

@reactjs/reactjs-org-korean-translation

현재 기존 페이지와 React 18관련해서 컨플릭트가 어머어머한데요. 한번 털고 가야할 듯 싶습니다. 어떻게 시작해야할까 고민인데 좋은 아이디어 스레드로 논의해보고 진행해보면 좋을 것 같습니다.

경로 : 문서 > 고급 안내서 > 코드 분할 > Avoiding fallbacks

Avoiding fallbacks 구문에 번역이 필요합니다.

I found broken url in 'docs/hooks-reference' page.

below is line 380
[메모이제이션된](https://ko.wikipedia.org/wiki/%EB%A9%94%EB%AA%A8%EC%9D%B4%EC%A0%9C%EC%9D%B4%EC%85%98n) 값을 반환합니다.

And you can check that url is not properly anchor to 메모이제이션 section of wikipedia page

https://ko.wikipedia.org/wiki/%EB%A9%94%EB%AA%A8%EC%9D%B4%EC%A0%9C%EC%9D%B4%EC%85%98n

So I'll fix it and PR it now.

Thanks.

I'm so sorry to say that, but I think that it might be better '것입니다' instead of '겁니다' in a page below.
https://ko.reactjs.org/docs/react-without-es6.html

보통 리액트 컴포넌트를 정의할 때 JavaScript의 class를 사용한다면 이와 같을 겁니다.

How do you guys think about this?

The followings are the missing docs in #1 .
번역 작업 목록( #1 )에 누락된 문서가 있어서 여기에 새로 목록을 추가했습니다.

• Legacy Context
• Legacy Event Pooling

https://reactjs.org/docs/reconciliation.html#recursing-on-children

React will mutate every child instead of realizing it can keep the <li>Duke</li> and <li>Villanova</li> subtrees intact. This inefficiency can be a problem.

AS-IS:
React는 모든 자식을 변형시켜 <li>Duke</li> 및 <li>Villanova</li> 서브 트리를 그대로 유지할 수 있음을 깨닫지 못합니다. 이러한 비효율은 문제가 될 수 있습니다.

TO-BE:
React는 <li>Duke</li> 및 <li>Villanova</li> 서브 트리를 그대로 유지할 수 있음을 알아차리는 것 대신에 모든 자식을 변형시킬 것입니다. 이러한 비효율은 문제가 될 수 있습니다.

React의 새로운 공식문서 번역이 시작되는 것 같습니다. 아래 스레드에서 논의가 진행되는 것 같은데 트래킹하면 좋을 것 같습니다.
A new official document translation of React seems to begin. The discussion seems to be taking place in the thread below, so it would be nice to track it.

reactjs/react.dev#4135 (comment)

I wrote a draft of "Best practices for translation" document. Will appreciate any feedback from you. :)
"번역 모범 사례" 문서의 초안을 작성해보았습니다. 보시고 의견있으시면 주세요. 어떤 피드백이든 환영합니다. :)

모범사례

쌍점은 거의 사용하지 않습니다.

한국어 맞춤법에서는 쌍점(colon, 콜론)을 사용하는 경우를 규정하고 있는데 항목의 열거나 희곡 대사 등에서만 제한적으로 사용합니다(참고). 특히 영어처럼 문장 끝에 쌍점을 붙이는 경우는 없으므로 주의하세요.

👍모범 사례
다음 예제를 보세요.

👎잘못된 사례
다음 예제를 보세요:

'시'는 제한적으로 사용합니다.

존칭을 표현하는 '-시-'는 문장의 간결함을 해칠 수 있습니다. ~하세요처럼 제한적인 경우에만 사용하고 그 외에는 사용하지 않는 편이 좋습니다. 다만, 작업자들끼리 대화할 때는 존중의 의미에서 사용해도 상관없습니다.

👍모범 사례
살펴보면 좋습니다.

👍모범 사례
살펴보세요.

👎잘못된 사례
살펴보시면 좋습니다.

쉼표를 모두 옮길 필요는 없습니다.

영어와 우리말에서 쉼표를 사용하는 사례가 다릅니다. 우리말에서 쉼표를 사용하는 몇 가지 경우는 맞춤법에 규정되어 있습니다. 꼭 필요할 때만 사용하고 그 외에는 제한하는 편이 좋을 것 같습니다.

🇬🇧For example, if `id` is the row ID, either of the following would work

👍모범 사례
예를 들어 `id`가 행의 ID일 경우 다음 코드가 모두 작동합니다.

👎잘못된 사례
예를 들어, `id`가 행의 ID일 경우 다음 코드가 모두 작동합니다.

render = 렌더링하다

render나 bind처럼 우리말 번역이 없고 원문의 음만 따서 쓰는 동사는 명사형 + ~하다로 번역하는 게 좋습니다.

🇬🇧 React renders DOM elements.

👍모범 사례
React는 DOM 엘리먼트를 렌더링합니다.

👎잘못된 사례
React는 DOM 엘리먼트를 렌더합니다.

👍모범 사례
함수를 바인딩해야 합니다.

당신과 여러분은 없어도 됩니다.

아주 가끔 꼭 필요할 때가 있기는 하지만 영어 표현에 많은 당신이나 여러분, 우리같은 표현은 안 쓰는 게 훨씬 자연스럽습니다.

🇬🇧 Let's say you want to output "Hello, world" in an DOM element.

👍모범 사례
DOM 엘리먼트에 "Hello, World"를 표현한다고 생각해봅시다.

👎잘못된 사례
당신이 DOM 엘리먼트에 "Hello, World"를 표현하고 싶다고 생각해봅시다.

피동형 문장에 주의하세요.

사실 원칙대로라면 ~되다같은 수동태도 가능하면 억제하는 편이 좋지만 실제로 작업을 하다 보면 써야 문장이 자연스러울 때도 있습니다. 다만 보여지다, 생각되다와 같은 불필요한 피동형 문장은 자제하는 편이 좋습니다.

🇬🇧 Elements appeared on the screen

👍모범 사례
화면에 보이는 엘리먼트

👎잘못된 사례
화면에 보여지는 엘리먼트

똑같은 표현은 비슷한 표현으로 대체하면 문장이 더 유려해집니다.

번역문에서 흔히 나타나는 문제가 영어 단어를 1:1로 번역하다 보니 표현이 단조로워진다는 점입니다. 예를 들어 common은 일반적으로라고만 번역한다거나 call은 호출한다라고만 번역하는 사례가 많습니다. 가까운 위치에서 똑같은 표현이 여러 차례 등장할 때 조금씩 표현을 바꾸어주면 문장이 더 읽기 좋아집니다. common이나 commonly는 일반적으로, 널리, 흔히 등으로 바꿀 수 있고 call, invoke 등은 호출하다, 실행하다 등으로 바꿀 수 있습니다.

👍모범 사례
이때 흔히 사용되는 패턴은 일반 자바스크립트 객체를 전달하는 것이다.

👎잘못된 사례
이때 일반적으로 사용되는 패턴은 일반 자바스크립트 객체를 전달하는 것이다. 

어색하지 않다면 단수형을 사용합시다.

원래 우리말에서는 ~들이라는 복수형 표현을 그리 널리 사용하지 않습니다. 물론 문장의 의미에 따라 반드시 복수의 객체임을 명시해야 할 때가 있긴 하지만, 그 외의 경우라면 단수형으로 표현하는 편이 대체로 자연스럽습니다.

🇬🇧 The examples below demonstrate the differences.

👍모범 사례
아래 예시는 위에서 언급한 차이점을 보여줍니다.

👍모범 사례 - 복수형 표현이 필요한 경우
아래 예시는 위에서 언급한 여러 차이점을 보여줍니다.

👎잘못된 사례
아래 예시들은 위에서 언급한 차이점들을 보여줍니다.

If는 생략할 수도 있습니다.

If로 시작하는 문장의 번역이 항상 만약으로 시작할 필요는 없습니다. 틀린 번역은 아니지만 한국어에서는 ~한다면이라는 어미가 이미 조건 또는 상황의 가정을 의미하므로 때로는 만약이 없어도 충분히 말이 됩니다. 아래 예시는 인접한 두 문장이 모두 만약으로 시작하고 있었습니다. 한 문장 만이라도 만약을 생략하면 조금 더 읽기 수월해집니다.

🇬🇧If you load React from a `<script>` tag, .... If you use ES6 with npm, ...

👍모범 사례
React를 <script> 태그로 불러온다면 ... ES6와 npm을 함께 사용한다면 ...

👎잘못된 사례
만약 React를 <script> 태그로 불러온다면 ... 만약 ES6와 npm을 함께 사용한다면 ...

https://github.com/reactjs/ko.reactjs.org/blob/f265301642079f05066231c005e73672eb2f0f91/content/docs/concurrent-mode-patterns.md

AS-IS
const [startTransition, isPending] = useTransition({

TO-BE
const [isPending, startTransition] = useTransition({

• 혹시, 아카이브된 문서라 업데이트가 이루어지지 않고 있나요?

    ko.reactjs.org/content/docs/reference-glossary.md

https://github.com/reactjs/ko.reactjs.org/blob/master/content/docs/reference-glossary.md

for better translation, translate glossary can help contributors understand how to translate technical terms.

pr merge

Since no PR has been merged yet, I think it would be good to make rule for merging PR.

pr template

<!--

Thank you for the PR! Contributors like you keep React awesome!

Please see the Contribution Guide for guidelines:

https://github.com/reactjs/reactjs.org/blob/master/CONTRIBUTING.md

If your PR references an existing issue, please add the issue number below

-->

here is the current PR template, but if the checklist is included here, contributors and reviewers can check the progress of the PR so it can bring better communicate better.

As you can see here, Universal Style Guide is added to reactjs/reactjs.org-translation.
I will translate this guide and add to this repo. The filename may be UNIVERSAL-STYLE-GUIDE.md

As we know, this project have many volunteers, and documents.

So, I think we need a board to share each work's status, blocking problems, etc.. also to prevent duplication of translation, and to work more effectively.

and, github issues and projects will do us.
could you share your idea about this?

I'm so sorry to mention about this, but the page 'create-a-new-react-app.html' doesn't show up whole contents of it on Chrome and IE also. (Part of the contents show up on the page)
I think that it's because of script tag(<script>) below.

It might be translated "<script>" tag instead of " `<script>` " text, so the browser treats it as a HTML tag.

• https://reactjs.org/docs/create-a-new-react-app.html

• https://ko.reactjs.org/docs/create-a-new-react-app.html

• PR #64 (line 25)

I think that it's better to modify that. ^^;

Translate Glossary 작성된 시점이 오래되었고 그에 따른 번역은 잘 이루어졌지만 그 이후 새로운 개념들이 들어왔고 (Suspense, Hydration 등) 그에 맞춘 새로운 번역어 합의가 제대로 이루어 지지 않음

생명주기(Lifecycle) / Lifecycle(생명주기) / Lifecycle(생명주기, 임시표기)

와 같은 형태로 #2 에서 번역 합의가 도출되기 전인 단어들의 통일된 임시 표기법을 정해 놓으면 이후 번역 속도 및 유지 관리 측면에서 좋을 것 같음

참고

#555 (comment)

@SyingSHY

어디에서 기여할 수 있을까요?

See Also:

• https://reactjs.org/blog/2022/03/29/react-v18.html

YouWillLearn, Gotcha, Recap, Challenges 와 같은 커스텀 태그 컴포넌트에 있는 영문 값들도 수정해주는 게 좋을 것 같다는 생각이 있습니다.
제가 번역을 진행한 Javascript in jsx with curly braces 에서 확인할 수 있는 컴포넌트는 이정도 있었습니다.

• Challenges

• ToC

• ExpandableCallout

• MDXComponent/YouWillLearn

Search feature does not works. Maybe API?

I'm so sorry, but there might be a typo on the page below.
(on Chrome, It doesn't show up on IE.)
https://ko.reactjs.org/docs/react-api.html
I think that 'ㄴㄴ' should be removed.

개요 > 컴포넌트 > React 컴포넌트를 사용하면 UI를 독립적이고 재사용할 수 있는 부분으로 나누고 각 부분을 분리하여 "생각할�� 수" 있습니다.

현재 한국문서 저장소가 outdated 되어있는 상태라 이걸 해결하고 싶습니다.

1. 어떤 작업을 해야할지 리스트를 작성
2. 베타 공식문서 번역에 관한 운영 방침 정의

Co-Worker: @MaxKim-J, @eomttt, @goofcode

Hi,
I am a beginner of react-hooks and I really appreciates for your translation works.

I found a small mistranslation in https://reactjs.org/docs/hooks-state.html#declaring-a-state-variable page.

• English version

What do we pass to useState as an argument? The only argument to the useState() Hook is the initial state. 
Unlike with classes, the state doesn’t have to be an object.
...

• Korean version

useState의 인자로 무엇을 넘겨주어야 할까요? useState()Hook의 인자로 넘겨주는 값은 state의 초기 값입니다.
함수 컴포넌트의 state는 클래스와 달리 객체를 가질 수 없고, 숫자 타입과 문자 타입을 가질 수 있습니다. 

the state doesn't have to be an object is translated as 객체를 가질 수 없고 for now,
but 객체일 필요가 없고 could be more correct one for this case.

Thanks.

It's not necessary, but Is it okay translate README.md as well?

"변역"을 "번역"으로 수정 바랍니다.

How to translate ?

Currently the beta website is in the beta folder.

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. 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 Discord #번역 channel if you are interested in the translation.

Check List

The new docs aren't fully written yet, and some parts will definitely change. However, a lot of the pages are already "stable". We suggest to use this checklist for the beginning. ✅ means "ok to translate", 🔴 means "don't translate yet".

• ✅ Installation (note: a lot of content here is similar to old website) (@hapumee) #386
  • ✅ Start a New React Project (@student513) #384
  • ✅ Add React to a Website (@LEEHYUNHO2001) #381
  • ✅ Editor Setup (@bugoverdose) #385
  • ✅ React Developer Tools
• 🔴 Quick Start (don't translate the index page yet, it will change)
  • ✅ Thinking in React (@hyunjaesung) #390
• 🔴 Describing the UI (don't translate the index page yet, it might change)
  • ✅ Your First Component (@h-yes-oo)
  • ✅ Importing and Exporting Components (@andyleeboo) #405
  • ✅ Writing Markup with JSX (@030ii) #393
  • ✅ JavaScript in JSX with Curly Braces (@alstn2468) #377
  • ✅ Passing Props to a Component (@kmin-jeong)
  • ✅ Conditional Rendering (@devdubby) #399
  • ✅ Rendering Lists (@jiseung-kang) #395
  • ✅ Keeping Components Pure (@BeomyeonAndrewKim)
• 🔴 Adding Interactivity (don't translate the index page yet, it might change)
  • ✅ Responding to Events (@KKonzi)
  • ✅ State: A Component's Memory (@heejour)
  • ✅ Render and Commit (@kimsangyeon) #394
  • ✅ State as a Snapshot (@h2ck4u) #396
  • ✅ Queueing a Series of State Updates (@hIkipooh)
  • ✅ Updating Objects in State (@wooooooood) #408
  • ✅ Updating Arrays in State (@n2ptune) #388
• 🔴 Managing State (don't translate the index page yet, it might change)
  • ✅ Reacting to Input with State (@woojenoh) #447
  • ✅ Choosing the State Structure
  • ✅ Sharing State Between Components (@devSoyoung) #398
  • ✅ Preserving and Resetting State (@atobaum) #389
  • ✅ Extracting State Logic into a Reducer (@jinsunee) #391
  • ✅ Passing Data Deeply with Context (@Jincy7) #400
  • ✅ Scaling Up with Reducer and Context (@cos22k) #404
• 🔴 Escape Hatches (not written yet)
  • ✅ Referencing Values with Refs (@dididy) #403
  • ✅ Manipulating the DOM with Refs (@Beingbook) #387
• Shared Component Translation (e.g. YouWillLearn, Gotcha) (@alstn2468) #383

Reference

• reactjs/react.dev#4135
• #373

우연찮게 발견하게 되었는데
Conflict가 된 상태 그대로 Merge가 되면서 문제가 생긴거 같습니다.

The remaining PR reviews are not being reviewed for a long time. Please give us your opinion on what to do from now on.

• 문제 페이지 : https://ko.reactjs.org/docs/hello-world.html
• Explorer에서는 정상적으로 표시되지만, Chrome에서는 이상하게 표시됩니다. 😢

안녕하세요 여러분.

React의 공식 베타문서가 릴리즈 됨에 따라 많은 변화가 생겼습니다.

• 기존 영문 문서는 legacy 저장소로 아카이빙 되고, react.dev라는 새로운 저장소가 만들어 졌습니다.
• #580 SYNC PR부터 beta folder가 사라지게 되었습니다. 이 PR을 머지하면, 기존에 작업했던 레거시 번역 페이지는 사라지게 됩니다. 현재 영문 문서와 동일한 정책을 가져가기엔 여러 제약이 있기 때문에 이 스레드에서 논의가 진행중입니다.
• 현재 번역되어있는 베타와 문서 릴리즈한 영문 문서 사이에 큰 차이가 있습니다. 이는 영문 문서의 컨텐츠 생성 속도가 번역 속도를 따라가지 못한 점과 관리가 잘 되지 못한 복합적인 이유로 발생했습니다.

따라서 환경의 변화가 큰 만큼 새로운 번역 환경을 만들어 보고자 합니다.

• 저장소 문제의 해결
  • 이 문제는 위에서 언급한 논의가 어느정도 방향성이 잡히면, 다시 논의해보면 좋을 것 같습니다.
• 기존에 번역했던 컨텐츠의 해결
  • 기존에 번역했던 컨텐츠를 살리는 것 보다는 양해를 구하고 다시 번역하는 편이 더 좋다는 생각이 듭니다. 기존에 번역을 진행하셨던 분들이 원하신다면, 먼저 배정을 드리고, 일정 기간이 지난 후 부터는 원하시는분께 새로 어사인 하는 정책이면 어떨까 하는생각입니다. 이 부분에 대해서는 의견 부탁드립니다. 🙇
• 번역에 대한 그라운드 룰 재정비
  • 기존에 그라운드 룰은 있었으나, 꽤 오래전에 작성되어있고 위키에 있어 접근성이 좋지 않기 때문에 잘 간과되고 지켜지고 있지 않았습니다.
  • 새 그라운드룰은 README.md에 작성 후 크게 두가지를 재정비 하고자 합니다.
    • Best practices for translation
    • Translate Glossary / (#569)

좋은 의견이 있으시면 언제든 스레드에 남겨주세요! 감사합니다.

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.

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

Basics

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

API Reference

• React (@cadenzah) #12
• React.Component (@cadenzah) #76
• ReactDOM (@noahluftyang) #28
• ReactDOMServer (@Injae-Lee) #68
• DOM Elements (@stepover10) #67
• SyntheticEvent (@Beingbook) #32
• Test Utilities (@ymin1103) #43
• Shallow Renderer (@hmu332233) #40
• Test Renderer (@hiddenest, @toy9910) #37, #190
• JS Environment Requirements (@taggon) #34
• 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.

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

Next Steps

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

Installation

• Getting Started (@MDJuniooor) #50
• Add React to a Website (@ymin1103) #101
• Create a New React App (@OnesQuared) #64
• CDN Links (@gnujoow) #44
• 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.

• Introducing Hooks (@Geon-wooBryanKim) #33
• Hooks at a Glance (@chatoo2412) #6
• Using the State Hook (@nghy97) #65
• Using the Effect Hook (@yumidev) #205
• Rules of Hooks (@BeomyeonAndrewKim) #63
• Building Your Own Hooks (@yumidev) #230
• Hooks API Reference (@hapumee) #89
• 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.

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

Advanced Guides

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

FAQ

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

Contributing

Priority: Low

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

Components

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

• CodeEditor (@taggon) #361
• CodeExample (@taggon) #361
• ErrorDecoder (@hIkipooh) #219
• LayoutFooter (@hoony2520) #122
• LayoutHeader (@AlexKoala) #56
• MarkdownPage (@dexterastin)

Additional Translations

These are not the primary translation targets.

• Blog
• Community

Translations added after this issue creation

Testing

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

Concurrent Mode (Experimental)

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

https://ko.reactjs.org/docs/strict-mode.html
페이지의 Ensuring reusable state 부분 번역이 필요합니다.

How about using some communication tools like slack? I wish there was a channel to exchange opinion. Say your ideas!

Thank you.

Hi there!

Congrats on almost finishing the Korean translation of the React docs. Before releasing, we have one more task to do. We need to change the DocSearch API key . One of the maintainers needs to sign up for DocSearch in order to do this.

Hi.

I followed instruction and had test as mentioned.

Test the change
If possible, test any visual changes in all latest versions of common browsers, on both desktop and mobile.
Run yarn check-all from the project root. (This will run Prettier, ESLint, and Flow.)

but, after i run yarn check-all, it automatically modifies two files and result to fail for textlint while committing it.

here is my logs...

➜  ko.reactjs.org git:(master) git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean`

➜  ko.reactjs.org git:(master) git checkout -b translate-uncontrolled-components
Switched to a new branch 'translate-uncontrolled-components'`

➜  ko.reactjs.org git:(translate-uncontrolled-components) yarn check-all
yarn run v1.7.0
$ npm-run-all prettier generate-ids --parallel lint flow
$ yarn format:source && yarn format:examples
$ prettier --config .prettierrc --write "{gatsby-*.js,{flow-typed,plugins,src}/**/*.js}"
flow-typed/gatsby.js 400ms
flow-typed/glamor.js 19ms
flow-typed/hex2rgba.js 14ms
flow-typed/react-helmet.js 10ms
flow-typed/slugify.js 8ms
gatsby-browser.js 34ms
gatsby-config.js 77ms
gatsby-node.js 15ms
plugins/gatsby-remark-header-custom-ids/gatsby-client.js 27ms
plugins/gatsby-remark-header-custom-ids/gatsby-ssr.js 34ms
plugins/gatsby-remark-header-custom-ids/index.js 33ms
plugins/gatsby-remark-use-jsx/index.js 17ms
plugins/gatsby-source-react-error-codes/gatsby-node.js 17ms
plugins/gatsby-transformer-authors-yaml/gatsby-node.js 18ms
plugins/gatsby-transformer-home-example-code/gatsby-node.js 17ms
plugins/gatsby-transformer-versions-yaml/create-redirects.js 29ms
plugins/gatsby-transformer-versions-yaml/gatsby-node.js 14ms
src/components/ButtonLink/ButtonLink.js 22ms
src/components/ButtonLink/index.js 8ms
src/components/CodeEditor/CodeEditor.js 76ms
src/components/CodeEditor/index.js 12ms
src/components/CodeExample/CodeExample.js 21ms
src/components/CodeExample/index.js 9ms
src/components/Container/Container.js 12ms
src/components/Container/index.js 6ms
src/components/ErrorDecoder/ErrorDecoder.js 34ms
src/components/ErrorDecoder/index.js 6ms
src/components/Flex/Flex.js 13ms
src/components/Flex/index.js 8ms
src/components/Header/Header.js 8ms
src/components/Header/index.js 7ms
src/components/Layout/index.js 6ms
src/components/Layout/Layout.js 14ms
src/components/LayoutFooter/ExternalFooterLink.js 10ms
src/components/LayoutFooter/Footer.js 45ms
src/components/LayoutFooter/FooterLink.js 13ms
src/components/LayoutFooter/FooterNav.js 13ms
src/components/LayoutFooter/index.js 9ms
src/components/LayoutHeader/DocSearch.js 34ms
src/components/LayoutHeader/Header.js 51ms
src/components/LayoutHeader/HeaderLink.js 19ms
src/components/LayoutHeader/index.js 7ms
src/components/LayoutHeader/SearchSvg.js 8ms
src/components/MarkdownHeader/index.js 6ms
src/components/MarkdownHeader/MarkdownHeader.js 9ms
src/components/MarkdownPage/index.js 6ms
src/components/MarkdownPage/MarkdownPage.js 31ms
src/components/StickyResponsiveSidebar/index.js 6ms
src/components/StickyResponsiveSidebar/StickyResponsiveSidebar.js 39ms
src/components/TitleAndMetaTags/index.js 7ms
src/components/TitleAndMetaTags/TitleAndMetaTags.js 9ms
src/html.js 12ms
src/pages/404.js 13ms
src/pages/acknowledgements.html.js 24ms
src/pages/blog/all.html.js 46ms
src/pages/docs/error-decoder.html.js 21ms
src/pages/index.js 58ms
src/pages/jsx-compiler.html.js 15ms
src/pages/languages.js 28ms
src/pages/versions.js 18ms
src/prism-styles.js 29ms
src/site-constants.js 8ms
src/templates/blog.js 16ms
src/templates/codepen-example.js 20ms
src/templates/community.js 14ms
src/templates/components/ChevronSvg/index.js 11ms
src/templates/components/ExternalLinkSvg/index.js 8ms
src/templates/components/MetaTitle/index.js 22ms
src/templates/components/NavigationFooter/index.js 9ms
src/templates/components/NavigationFooter/NavigationFooter.js 31ms
src/templates/components/Sidebar/index.js 9ms
src/templates/components/Sidebar/ScrollSyncSection.js 28ms
src/templates/components/Sidebar/Section.js 20ms
src/templates/components/Sidebar/Sidebar.js 13ms
src/templates/docs.js 12ms
src/templates/tutorial.js 10ms
src/theme.js 53ms
src/types.js 9ms
src/utils/createLink.js 18ms
src/utils/createOgUrl.js 9ms
src/utils/findSectionForPath.js 10ms
src/utils/isItemActive.js 9ms
src/utils/loadScript.js 7ms
src/utils/patchDOMForGoogleTranslate.js 10ms
src/utils/sectionList.js 8ms
src/utils/slugify.js 7ms
src/utils/toCommaSeparatedList.js 12ms
$ prettier --config examples/.prettierrc --write "examples/**/*.js"
examples/16-3-release-blog-post/context-example.js 392ms
examples/16-3-release-blog-post/create-ref-example.js 17ms
examples/16-3-release-blog-post/fancy-button-example.js 15ms
examples/16-3-release-blog-post/forward-ref-example.js 30ms
examples/16-3-release-blog-post/hoc-theme-example.js 10ms
examples/16-4-release-blog-post/pointer-events-example.js 52ms
examples/components-and-props/composing-components.js 12ms
examples/components-and-props/extracting-components-continued.js 29ms
examples/components-and-props/extracting-components.js 36ms
examples/components-and-props/rendering-a-component.js 9ms
examples/context/motivation-problem.js 10ms
examples/context/motivation-solution.js 11ms
examples/context/multiple-contexts.js 17ms
examples/context/reference-caveats-problem.js 8ms
examples/context/reference-caveats-solution.js 11ms
examples/context/theme-detailed-app.js 22ms
examples/context/theme-detailed-theme-context.js 12ms
examples/context/theme-detailed-themed-button.js 10ms
examples/context/updating-nested-context-app.js 14ms
examples/context/updating-nested-context-context.js 6ms
examples/context/updating-nested-context-theme-toggler-button.js 8ms
examples/es5-syntax-example.js 8ms
examples/forwarding-refs/customized-display-name.js 11ms
examples/forwarding-refs/fancy-button-ref.js 7ms
examples/forwarding-refs/fancy-button-simple-ref.js 8ms
examples/forwarding-refs/fancy-button-simple.js 6ms
examples/forwarding-refs/fancy-button.js 6ms
examples/forwarding-refs/log-props-after.js 11ms
examples/forwarding-refs/log-props-before.js 8ms
examples/forwarding-refs/wrapped-component-with-function-name.js 6ms
examples/forwarding-refs/wrapped-component.js 6ms
examples/hello-world.js 6ms
examples/introducing-jsx.js 9ms
examples/jsx-simple-example.js 6ms
examples/react-component-reference/get-snapshot-before-update.js 11ms
examples/reconciliation/index-used-as-key.js 25ms
examples/reconciliation/no-index-used-as-key.js 27ms
examples/reference-react-forward-ref.js 11ms
examples/rendering-elements/render-an-element.js 7ms
examples/rendering-elements/update-rendered-element.js 10ms
examples/strict-mode/enabling-strict-mode.js 12ms
examples/strict-mode/side-effects-in-constructor.js 7ms
examples/tutorial-expanded-version.js 7ms
examples/uncontrolled-components/input-type-file.js 13ms
examples/update-on-async-rendering/adding-event-listeners-after.js 12ms
examples/update-on-async-rendering/adding-event-listeners-before.js 9ms
examples/update-on-async-rendering/adding-event-listeners-create-subscription.js 12ms
examples/update-on-async-rendering/definition-getderivedstatefromprops.js 7ms
examples/update-on-async-rendering/definition-getsnapshotbeforeupdate.js 7ms
examples/update-on-async-rendering/fetching-external-data-after.js 11ms
examples/update-on-async-rendering/fetching-external-data-before.js 10ms
examples/update-on-async-rendering/initializing-state-after.js 6ms
examples/update-on-async-rendering/initializing-state-before.js 9ms
examples/update-on-async-rendering/invoking-external-callbacks-after.js 6ms
examples/update-on-async-rendering/invoking-external-callbacks-before.js 14ms
examples/update-on-async-rendering/react-dom-properties-before-update-after.js 9ms
examples/update-on-async-rendering/react-dom-properties-before-update-before.js 10ms
examples/update-on-async-rendering/side-effects-when-props-change-after.js 7ms
examples/update-on-async-rendering/side-effects-when-props-change-before.js 6ms
examples/update-on-async-rendering/updating-external-data-when-props-change-after.js 12ms
examples/update-on-async-rendering/updating-external-data-when-props-change-before.js 12ms
examples/update-on-async-rendering/updating-state-from-props-after.js 6ms
examples/update-on-async-rendering/updating-state-from-props-before.js 6ms
examples/update-on-async-rendering/using-react-lifecycles-compat.js 8ms
$ node scripts/generateHeadingIDs.js content
$ flow
$ eslint .
Launching Flow server for /Users/sukjaelee/open-source-project/ko.reactjs.org
Spawned flow server (pid=91711)
Logs will go to /private/tmp/flow/zSUserszSsukjaeleezSopen-source-projectzSko.reactjs.org.log
No errors!
✨  Done in 10.61s.

➜  ko.reactjs.org git:(translate-uncontrolled-components) ✗ git status
On branch translate-uncontrolled-components
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   content/community/conferences.md
	modified:   content/docs/hooks-faq.md

no changes added to commit (use "git add" and/or "git commit -a")

➜  ko.reactjs.org git:(translate-uncontrolled-components) ✗ git add -A
➜  ko.reactjs.org git:(translate-uncontrolled-components) ✗ git commit -m "Translated docs/uncontrolled-components page"
husky > pre-commit (node v8.11.1)
  ↓ Stashing changes... [skipped]
    → No partially staged files found...
  ❯ Running linters...
    ❯ Running tasks for *.md
      ✖ textlint --rulesdir textlint/rules



✖ textlint --rulesdir textlint/rules found some errors. Please fix them and try committing again.

/Users/sukjaelee/open-source-project/ko.reactjs.org/content/docs/hooks-faq.md
 64:80   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
121:54   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
140:208  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
189:38   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
220:44   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
240:171  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
254:270  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
263:184  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
283:143  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
297:150  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
325:92   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
341:73   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
376:170  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
416:95   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
439:173  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
457:271  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
482:100  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
536:268  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
550:96   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
572:190  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
591:174  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
611:94   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
631:96   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
635:256  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
659:174  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
676:357  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
697:227  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
723:83   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
737:152  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
749:77   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
772:76   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
782:89   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
794:180  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
804:147  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
833:82   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
841:178  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
858:163  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
875:105  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
904:444  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
929:166  error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon
976:54   error  문장 끝에 쌍점(:)과 쌍반점(;)은 사용하지 않습니다  no-endline-colon

✖ 41 problems (41 errors, 0 warnings)

husky > pre-commit hook failed (add --no-verify to bypass)

Related to #270 (comment)

When I'm resolving syn pull request #270, I find that some original text are lost. we need to add translation.

• English
• Korean

React.Component's componentDidCatch

Production and development builds of React slightly differ in the way componentDidCatch() handles errors.

On development, the errors will bubble up to window, this means that any window.onerror or window.addEventListener('error', callback) will intercept the errors that have been caught by componentDidCatch().

On production, instead, the errors will not bubble up, which means any ancestor error handler will only receive errors not explicitly caught by componentDidCatch().

There are some Korean translations of official React documents. I think we can translate them a little bit faster if we can use the previously translated text. So, I list the translation posts that are accessible by URL but are not committed in the current repository. The translation lists are listed in the latest order of publication date. The pages that did not find translations are not listed below.

If you would like to recommend another translation, please let me know by comment. I will update the description of this issue.

⚠️ Please note that this does not mean that you "must use" the following listed translations. The translations can also be protected by copyright, so if you want to refer to them, it's a good way to work with permission in advance. Please respect the translator who worked in advance.

Core Pages 📖

• Home Page
  • https://reactjs-org-ko.netlify.com/
  • https://reactjs-kr.firebaseapp.com/
• Tutorial
  • https://reactjs-org-ko.netlify.com/tutorial/tutorial.html
  • https://reactjs-kr.firebaseapp.com/tutorial/tutorial.html

Basics

• Hello World
  • https://www.gaesignerblog.com/post/13
  • https://reactjs-kr.firebaseapp.com/docs/hello-world.html
• Introducing JSX
  • https://www.gaesignerblog.com/post/14
  • https://reactjs-kr.firebaseapp.com/docs/introducing-jsx.html
• Rendering Elements
  • https://www.gaesignerblog.com/post/17
  • https://reactjs-org-ko.netlify.com/docs/rendering-elements.html
  • https://reactjs-kr.firebaseapp.com/docs/rendering-elements.html
• Components and Props
  • https://www.gaesignerblog.com/post/18
  • https://reactjs-org-ko.netlify.com/docs/components-and-props.html
  • https://reactjs-kr.firebaseapp.com/docs/components-and-props.html
• State and Lifecycle
  • https://www.gaesignerblog.com/post/24
  • https://reactjs-kr.firebaseapp.com/docs/state-and-lifecycle.html
• Handling Events
  • https://www.gaesignerblog.com/post/26
  • https://reactjs-org-ko.netlify.com/docs/handling-events.html
  • https://reactjs-kr.firebaseapp.com/docs/handling-events.html
• Conditional Rendering
  • https://www.gaesignerblog.com/post/27
  • https://reactjs-org-ko.netlify.com/docs/conditional-rendering.html
  • https://reactjs-kr.firebaseapp.com/docs/conditional-rendering.html
• Lists and Keys
  • https://www.gaesignerblog.com/post/28
  • https://reactjs-org-ko.netlify.com/docs/lists-and-keys.html
  • https://reactjs-kr.firebaseapp.com/docs/lists-and-keys.html
• Forms
  • https://www.gaesignerblog.com/post/29
  • https://reactjs-org-ko.netlify.com/docs/forms.html
  • https://reactjs-kr.firebaseapp.com/docs/forms.html
• Lifting State Up
  • https://www.gaesignerblog.com/post/30
  • https://reactjs-org-ko.netlify.com/docs/lifting-state-up.html
  • https://reactjs-kr.firebaseapp.com/docs/lifting-state-up.html
• Composition vs Inheritance
  • https://www.gaesignerblog.com/post/33
  • https://reactjs-org-ko.netlify.com/docs/composition-vs-inheritance.html
  • https://reactjs-kr.firebaseapp.com/docs/composition-vs-inheritance.html
• Thinking in React
  • https://www.gaesignerblog.com/post/34
  • https://reactjs-org-ko.netlify.com/docs/thinking-in-react.html
  • https://reactjs-kr.firebaseapp.com/docs/thinking-in-react.html

API Reference

• React
• React.Component
  • https://reactjs-org-ko.netlify.com/docs/react-component.html
• ReactDOM
• ReactDOMServer
  • https://www.gaesignerblog.com/post/63
• DOM Elements
• SyntheticEvent
• Test Utilities
• Shallow Renderer
• Test Renderer
• JS Environment Requirements
• Glossary
  • Check out #2

Navigation

• tutorial/nav.yml
  • https://reactjs-kr.firebaseapp.com/tutorial/tutorial.html
• docs/nav.yml
  • https://reactjs-org-ko.netlify.com/docs/hello-world.html
  • https://reactjs-kr.firebaseapp.com/docs/hello-world.html

Next Steps 📖

Installation

• Getting Started
  • https://reactjs-kr.firebaseapp.com/docs/installation.html#react-%EC%8B%9C%EC%9E%91%ED%95%98%EA%B8%B0
• Add React to a Website
• Create a New React App
  • https://reactjs-kr.firebaseapp.com/docs/installation.html#creating-a-new-application
• CDN Links
  • https://reactjs-kr.firebaseapp.com/docs/installation.html#cdn-%EC%82%AC%EC%9A%A9%ED%95%98%EA%B8%B0

Hooks

• Introducing Hooks
• Hooks at a Glance
  • https://chatoo2412.github.io/javascript/react/react-hooks-overview/
• Using the State Hook
• Using the Effect Hook
• Rules of Hooks
• Building Your Own Hooks
• Hooks API Reference
• Hooks FAQ

Advanced Guides

• Accessibility
  • https://www.gaesignerblog.com/post/47
• Code-Splitting
  • https://www.gaesignerblog.com/post/51
• Context
  • http://www.gaesignerblog.com/post/55
  • https://reactjs-org-ko.netlify.com/docs/context.html
  • https://reactjs-kr.firebaseapp.com/docs/context.html
• Error Boundaries
  • https://www.gaesignerblog.com/post/57
  • https://reactjs-kr.firebaseapp.com/docs/error-boundaries.html
• Forwarding Refs
  • https://www.gaesignerblog.com/post/60
• Fragments
  • https://www.gaesignerblog.com/post/70
  • https://reactjs-kr.firebaseapp.com/docs/fragments.html
• Higher-Order Components
  • https://reactjs-org-ko.netlify.com/docs/higher-order-components.html
  • https://reactjs-kr.firebaseapp.com/docs/higher-order-components.html
• Integrating with Other Libraries
  • https://www.gaesignerblog.com/post/72
• JSX In Depth
  • https://reactjs-org-ko.netlify.com/docs/jsx-in-depth.html
  • https://reactjs-kr.firebaseapp.com/docs/jsx-in-depth.html
• Optimizing Performance
  • https://reactjs-org-ko.netlify.com/docs/optimizing-performance.html
  • https://reactjs-kr.firebaseapp.com/docs/optimizing-performance.html
• Portals
  • https://www.gaesignerblog.com/post/76
  • https://reactjs-kr.firebaseapp.com/docs/portals.html
• React Without ES6
  • https://reactjs-kr.firebaseapp.com/docs/react-without-es6.html
• React Without JSX
  • https://reactjs-kr.firebaseapp.com/docs/react-without-jsx.html
• Reconciliation
  • https://reactjs-org-ko.netlify.com/docs/reconciliation.html
  • https://reactjs-kr.firebaseapp.com/docs/reconciliation.html
• Refs and the DOM
  • https://reactjs-org-ko.netlify.com/docs/refs-and-the-dom.html
  • https://reactjs-kr.firebaseapp.com/docs/refs-and-the-dom.html
• Render Props
  • https://medium.com/@la.place/react-render-props-pattern-1c53a6b9645c
• Static Type Checking
  • https://reactjs-kr.firebaseapp.com/docs/static-type-checking.html
• Strict Mode
• Typechecking With PropTypes
  • https://reactjs-kr.firebaseapp.com/docs/typechecking-with-proptypes.html
• Uncontrolled Components
  • https://reactjs-org-ko.netlify.com/docs/uncontrolled-components.html
  • https://reactjs-kr.firebaseapp.com/docs/uncontrolled-components.html
• Web Components

Additional Information

• https://reactjs-kr.firebaseapp.com/*
  • All links have been translated based on React version v16.2.0.
  • Those have not been maintained since January 22, 2018.
  • See comparing changes with reactjs/reactjs.org
• reactkr/discuss #4
  • This is a translation related thread that was attempted by the React community in Korea.
  • But it does not seem to be maintained based on this issue after React v0.14.0-alpha.
  • You can see related branches.
    • https://github.com/reactkr/react/tree/reactkr
    • https://github.com/reactkr/react/tree/translation-v15
    • https://github.com/reactkr/react/tree/translation
• https://reactjs-org-ko.netlify.com/*
  • This repository (branch: ko-kr-180116) is fork of https://reactjs-kr.firebaseapp.com/
  • Some fixes are included.
  • See comparing changes with upstream repository.

작업내용

• React.suspense 문서 링크 단락의 미번역된 문서 번역을 추가합니다.

• React.startTransition 문서 링크 단락의 미번역된 문서 번역을 추가합니다.

안녕하세요! 위 두 내용 번역을 추가해보고 싶은데 혹시 현재 번역중이신 분이 계실까요? 🙇‍♂️
미번역된 내용이 많지는 않아, 현재 배정된 분이 계시지 않는다면 제가 기여해보고자 합니다 🙏

Regarding the scope of translation, we need to discuss what to translate and what not to translate.

Any suggestion?