OLD CLAIMS

[reactjs]

OLD CLAIMS

[hijiangtao]

We may need a better structure to organize the translation list, it's pretty difficult to see the progress of it, currently.

For example, use table rather than list:

Title	Processing	Status
Hello World	(@ GitHub ID here)	Translating/Proofreading, etc.

[tesseralis]

@QC-L I hope you don't mind if I updated the issue a bit to make it consistent with the other translation efforts :)

[yuqingc]

I'd like to claim the "tutorial" part if it is not taken yet.

[hijiangtao]

🎉 Thanks for all of your enthusiastic participation in React Simplified Chinese Documents, and let's follow current guidance (given in the beginning by @QC-L) - Take only one page at a time, to make the translation work more consistent and organized.

You can claim again after a PR is raised for your current translation. Currently, we regard the first article in each comment as your current translation claim.

You are also welcomed to give your estimated time or date for your translation claims, such as:

EST.cmplt Date: 2019.02.14

or

EST.cmplt Time: within 2 days

Then we can keep an eye on it and give you helps when it's necessary.

[hateonion]

Title	Processing	Status
AJAX and APIs	@hateonion	Translating

[ChiuMungZitAlexander]

Looks like there're only a few left. So how about I take Virtual DOM and Internals?

Title	Processing	Status
Virtual DOM and Internals	@ChiuMungZitAlexander	Translating

[CoolRice]

Title	Processing	Status
Components/ErrorDecoder	@CoolRice	Translating

[QC-L]

@robertying The previous content did not have some review, this time will pay attention, thank you for reminding.
Thank you for your help, make this repo perfect.

[caiyongmin]

I'd like to claim the Test Utilities part if it is not taken yet.

[pppluto]

Pleasure to translate Conditional Rendering

[baxtergu]

Would like to take Lifting State Up as a start.

Title	Processing	Status
Basics / Lifting State Up	@baxtergu	#90

[cyanial]

Want to start at State and Lifecycle.

[robertying]

Continue with Composition vs Inheritance, if it's ok

[haimengzhang]

Is anyone planning to translate Introduction to JSX?

…

On Fri, Feb 1, 2019 at 3:19 AM Robert Ying ***@***.***> wrote: Continue with Composition vs Inheritance, if it's ok — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATTNC2cNZh74lAbPJhQgU3fTN886NKaxks5vJAaMgaJpZM4acNVY> .

[robertying]

I'll continue to work on Rendering Elements.

[zhaozhiming]

I will claim the Lists and Keys if it is not taken yet.

[Ryanhui]

I will translate Handling Events

[zhangxd6]

I would like to try the form if it is not taken

[BetaMee]

Title	Processing	Status
Context	@BetaMee	Proofreading
Code-Splitting	@BetaMee	Proofreading

[Ryanhui]

Title	Pocessing	Status
API Reference/JS Environment Requirements	@Ryanhui	Translating

[Ryanhui]

Title	Pocessing	Status
API Reference/Shallow Renderer	@Ryanhui	Translating

[baxtergu]

Title	Processing	Status
API Reference / React	@baxtergu	#138

[Ryanhui]

Title	Processing	Status
API Reference / ReactDOM	@Ryanhui	Translating

[laozhu]

Title	Processing	Status
Installation / Getting Started	@laozhu	#143

[lixiaoyang1992]

Title	Processing	Status
Hooks / Introducing Hooks	@lixiaoyang1992	#131

[zbc]

Title	Processing	Status
API Reference / DOM Elements	@zbc	Translating

[ChloeLiang]

Title	Processing	Status
API Reference / Test Renderer	@ChloeLiang	Translating

[Ryanhui]

Title	Processing	Status
API Reference / SyntheticEvent	@Ryanhui	Translating

[haimengzhang]

Title	Processing	Status
API Reference / React.Component	@haimengzhang	TimeOut

[bailnl]

I can take Building Your Own Hooks, if no one is

Title	Processing	Status
Hooks / Building Your Own Hooks	@bailnl	Translating

[pampang]

I would like to take API Reference / ReactDOMServer, if it is not taken.

Title	Processing	Status
API Reference / ReactDOMServer	@pampang	#100

[yesmeck]

I'd like to take Hooks / Hooks at a Glance.

Title	Processing	Status
Hooks / Hooks at a Glance	@yesmeck	Translating

[chenshuai2144]

I'd like to take Render Props and Fragments

[ycjcl868]

I'd like to take Static Type Checking and Typechecking With PropTypes

Title	Processing	Status
Docs / Typechecking With PropTypes	@ycjcl868	#108
Docs / Static Type Checking	@ycjcl868	#116

[seognil]

Title	Processing	Status
Installation / Add React to a Website	@seognil	#103
Installation / Create a New React App	@seognil	#104

[Crazydogs]

I'd like to take Using the Effect Hook and Rules of Hooks

Title	Processing	Status
Hooks/ Using the Effect Hook	@Crazydogs	Translating
Hooks/ Rules of Hooks	@Crazydogs	Translating

[Yuiham]

I'd like to take Hooks API Reference

Title	Processing	Status
Hooks/ Hooks API Reference	@Yuiham	#173

[thewashingtonhua]

I'd like to take Hooks/Hooks FAQ

Title	Processing	Status
Hooks/Hooks FAQ	@tonghuashuo	#121

[zombieJ]

volunteer for Using the Effect Hook

Update: volunteer for Optimizing Performance

[dear-lizhihua]

I'd like to take Glossary of React Terms
https://reactjs.org/docs/glossary.html

Title	Processing	Status
Glossary of React Terms	@ dear-lizhihua	Translating

[seognil]

Title	Processing	Status
warnings/invalid-aria-prop	@seognil	#114
warnings/legacy-factories	@seognil	#113
warnings/special-props	@seognil	#112

I'd use permalink from .md for title of warning sections
(these three are shortest LOL

[yhsunshining]

could I take Advanced Guides/Forwarding Refs?

Title	Processing	status
Advanced Guides/Forwarding Refs	@yhsunshining	Translating

[seognil]

Title	Processing	Status
warnings/dont-call-proptypes	@seognil	#115
warnings/invalid-hook-call-warning	@seognil	#169
warnings/refs-must-have-owner	@seognil	#124
warnings/unknown-prop	@seognil	#111

warnings/invalid-hook-call-warning is missed from the list at top
(it's positioned at No.3 in warning section by alphabet)

[LCINA]

I'd like to take Error Boundaries

Title	Processing	Status
Error Boundaries	@LCINA	Translating

[ttys026]

Title	Processing	Status
Advanced Guides / Uncontrolled Components	@tli4	Translating

[summccc]

I'd like to take Accessibility please.

Timeout.

[sang4lv]

Title	Processing	Status
Reconciliation	@sang4lv	#122

[bailnl]

I'd like to take web components ， if no one is.

Title	Processing	Status
Advanced Guides / web components	@bailnl	Translating

[zbc]

Title	Processing	Status
Portals	@zbc	Translating

[sang4lv]

I'll take HOC and Portals

Title	Processing	Status
Higher-Order Components	@sang4lv	Translating
Integrating with Other Libraries	@sang4lv	Translating

[pampang]

Title	Processing	Status
refs and the dom	@pampang	#154

[zhaozhiming]

Title	Processing	Status
React Without ES6	@zhaozhiming	#128

[postor]

I'll take Integrating with Other Libraries

Title	Processing	Status
Integrating with Other Libraries	@postor	#129

[fonkie]

I'll take Strict Mode

Title	Processing	Status
Strict Mode	@fonkie	#165

[nanaSun]

Title	Processing	Status
Codebase Overview	@nanaSun	#144

[QC-L]

Title	Processing	Status
Babel, JSX, and Build Steps	@QC-L	Translating

[bbbbx]

I volunteer to translate:

Title	Processing	Status
Component State	@bbbbx	#137

[infinnie]

I take:

Title	Processing	Status
Styling and CSS	@infinnie	#134

[sichenguo]

could I take FAQ/Passing Functions to Components?

Title	Processing	status
Passing Functions to Components	@sichenguo	Translating

[buffaybu]

I'd like to take Versioning Policy.

Title	Processing	Status
Versioning Policy	@buffaybu	#139

[baxtergu]

Title	Processing	Status
FAQ / File Structure	@baxtergu	#148

[thjttk]

Title	Processing	Status
Contributing/Design Principles	@TangHeJun	#145

[musclejack]

Title	Processing	Status
React.Component	@musclejack	Translating

[zcfan]

I'll work on "Hooks state" since @Koopos is inactive.

Title	Processing	Status
Hooks/ Using the State Hook	@zcfan	Translating

[jimczj]

Title	Processing	Status
Contributing/ How to Contribute	@jimczj	Translating

[nanaSun]

I'll take Implementation Notes

Title	Processing	Status
Implementation Notes	@nanaSun	Translating

[zcfan]

Title	Processing	Status
CodeEditor	@zcfan	#149

[zcfan]

Title	Processing	Status
CodeExample	@zcfan	#150

[hstarorg]

Title	Processing	Status
jsx-in-depth	@hstarorg	#158

[maicss]

Titel	Processing	Status
blog/You Probably Don't Need Derived State	@maicss	Translating

[EthanP-CN]

I'd like to claim the blog "2019-02-23-is-react-translated-yet" if it is not taken yet.

[robertying]

I would like to translate, starting with “Thinking in React” if that’s ok.

But we need to wait for the glossary to be finished first, don’t we? Or is there anything I can help with too?

[tesseralis]

@robertying I think you can start. The previous version of the glossary is here for reference: https://react.docschina.org/docs/glossary.html

Remember to reference the previous version of the translation (https://react.docschina.org/docs/thinking-in-react.html) and just make sure it's accurate to the current docs (https://reactjs.org/docs/thinking-in-react.html

[robertying]

@tesseralis their original work seems more than intact. Translating those pages would be mostly reviewing instead of editing. I don’t tend to take their credit for those. Maybe I should start with something untranslated like pages about hooks. What do you think?

[tesseralis]

Sure! I think some of the hooks pages are already translated but you're free to pick one that isn't :)

[robertying]

I’ll start from bottom to top so the first will be “Hooks FAQ” 😊

[tesseralis]

@QC-L are you and the team able to handle porting over the rest of the Chinese site in the next few weeks? Would you like folks like @robertying to help?

[QC-L]

@tesseralis I will give the translation process and specifications.
I will work overtime recently to do the job.

[QC-L]

@robertying You can choose one, if you think it is not good before, you can re-translate.

[robertying]

@QC-L Would you like me to review old ones first or start new translations?

[lcxfs1991]

Happy to see your enthusiasm @robertying. There seems to be some defects in old version because reviewer did not review in time. Though we should be thankful since a lot of people voluntarily help the translation. Open source community needs both hero and the mass.

Looking forward to your contribution!

[QC-L]

@robertying Past content can be referenced, but re-translation is best.
We should respect the fruits of the community's work.

[robertying]

Cool, thanks for the suggestions. 😀 After careful considerations, I think I'd better start to review the old ones first so the website can get working soon. As was mentioned, I'll start from bottom to top. The first would be reviewing Thinking in React.

[QC-L]

Yeah, that's great.
I will add the QR code of the WeChat group in README.md.
You can join us, as @lcxfs1991 says the community need hero.

[QC-L]

@robertying See README.md

[QC-L]

@haimengzhang You can translate it.

[Koopos]

anyone working on using state hooks?

[QC-L]

@Koopos We focus on Basics, but you can try it first.

[tesseralis]

Could one of the maintainers mark which pages have pull requests for them? e.g.

• Tutorial (@yuqingc) #12

[QC-L]

@tesseralis OK, I changed it.

[QC-L]

@zcfan NO, you can review this PR #16

[Runbo94]

I'll take Implementation Notes

Title
Processing
Status

Implementation Notes
@nanaSun
Translating

你翻译多少了。。。我翻译到 Updating{#updating}了

[QC-L]

@Runbo94 Please submit the content after receiving the task next time, thank you for your cooperation.😝

[YaokaiYang-assaultmaster]

Hey there, looks like all the parts have been taken. Are there any sections I can help about? Please let me know and I am definitely willing to help. @QC-L

[QC-L]

@YaokaiYang-assaultmaster That's great. You can review the translated articles. Prioritize articles in Basics and API Reference.

[maicss]

Title Processing Status
React.Component @musclejack Translating

hi，你翻译多少啦？

[Somiona]

Hi, can I take any of blog pages? It seems like all the "Primary" tasks are already taken.

[QC-L]

@CalElFe Yeah, that's awesome. I'll add blog related content. You can try.

[maicss]

@QC-L 我想问一下，如果英文的文档更新了，那到时候怎么记录差异，然后更新中文文档呢？

[QC-L]

@maicss I will solve the difference problem.