Is React Translated Yet?
summary
Official docs are now live in 40 languages, achieved by rejecting Crowdin in favor of a GitHub repo per language workflow, automated repo creation via the GitHub REST API, a simple sync bot run with Unix cron, and a progress website. Hundreds of volunteers — about 180+ contributors and maintainers — do reviews; initial rate-limit mistakes even get one account suspended but the automation and merge/PR strategy keep translations up to date and working.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:29Political Intrigue!
- 2:36Allow non-English speakers to write code 2. ???
- 3:58Allow non-English speakers to write code 2. Give official sponsorship/support to translations
- 5:58Easy for translators for contribute
- 9:50three (3)
- 10:46Keep it simple
- 12:02Get the hard stuff sorted out early
- 15:17Remove Friction
- 15:39Get people motivated!
- 16:03Have a system in place
- 16:27Give ownership
- 17:47Be patient, be kind, be helpful
- 20:12LIES
- 21:13Done is better than perfect
- 22:07Trust (but verify)
- 22:33Quality localization takes effort
- 22:53localization === accessibility
- 23:40How can you help translate React?
- 23:59React Team
related talks
46mTackling Language Barriers in Open Source Docs: A Case Study of openEuler's...
36mOpen Source at Scale
35mOpen Source at Scale
28mLet React speak your language
22mRe-inventing the Rosetta Stone Together
28mOpensource Documentation—Tales from React and React Native
26mBoost your developer site with localisation
39mOpen Docs, Open Collaboration: Building Better Documentation with Community PRs