Enhancement: CrowdIn localization intregration

[ericnakagawa]

Description

The React website uses Gatsby for a fantastic user experience. React's docs are drafted in English, however millions of potential developers outside the US have been asking for ways to make the documentation accessible to non-english speaking audience. Currently, we have much of the site's content almost completely translated by the international community on the CrowdIn React translation project.

Crowdin provides free accounts for open source projects. My team at Facebook Open Source has enabled localization on several of our large and growing projects.

I'd love to see support, guides, or even walkthroughs for adding crowdin localization to gatsby sites like React.

[m-allanson]

Yes @ericnakagawa! Do you know if there's a write-up on how CrowdIn was implemented on the React website? It'd make a good post for the Gatsby blog or tutorial section of the docs.

Also a CrowdIn Gatsby starter could be useful, to join the existing i18n starters. And there's a long discussion on internationalising Gatsby websites.

[KyleAMathews]

@m-allanson he's looking for help in localizing reactjs.org — they haven't done it yet.

[m-allanson]

Ah ok! It'd be great to get examples from someone who's implemented CrowdIn for a Gatsby site.

[gedeagas]

@KyleAMathews we are translating it on https://crowdin.com/project/react.

but because there is no official support yet to enable multiple languages in gatsby our hard work translating ReactJS is not yet live in the ReactJS website :(.

[bvaughn]

Hi 👋

Myself and @clemmy worked on integration a bit back in November but were unable to finish. At the time, we created a new Gatsby plug-in, gatsby-plugin-crowdin, that we were hoping to get plugged into the ReactJS.org site.

You can see our work in progress here if you'd like: reactjs/react.dev/pull/873

I am planning to spend a little time today and tomorrow trying to bring myself back up to speed on where we left off and what more needs to be done to finish.

[gedeagas]

Thank you for your hard work @bvaughn. That is a great news for us. please tell us when it finished

[clemmy]

@bvaughn Lemme know if you need some help! I just came back from my grad trip and can use some de-rusting. 😆

[gatsbot]

Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open!

[gatsbot]

This issue is being closed due to inactivity. Is this a mistake? Please re-open this issue or create a new issue.

[samajammin]

@ericnakagawa I'm curious, does React and/or Facebook use CrowdIn for translations? I see you're still the owner of the React project but it looks like you folks may have moved entirely to Github? I would love to learn the approach your taking with Calibra. Appreciate anything you could share :)

[samajammin]

I'd also love to know if there's any update on a Gatsby plugin or starter for CrowdIn. I searched for both but didn't find any on gatsbyjs.org. Thanks all!

[bvaughn]

I'd also love to know if there's any update on a Gatsby plugin or starter for CrowdIn.

No update on this, unfortunately. I ended up getting distracted by other project. @tesseralis took over the translation/localization efforts for reactjs.org.

[tesseralis]

@samajammin we decided on a GitHub-based approach. I'm actually working with Gatsby to do their translations and decided on the same approach. You can see my thoughts here: https://github.com/gatsbyjs/rfcs/pull/42/files

In short:

• Our translations are sourced from the developer community, and most of them prefer Git.
• Crowdin has some trouble handling markdown content, leading to sometimes mismatched tags.
• Crowdin's (English) documentation quality is lacking.
• This approach takes some effort to get started since you need to build automation for it.

It all depends who's doing your translations and what they prefer, and whether you have the dev-power to build that automation (feel free to check React's out at https://github.com/reactjs/reactjs.org-translations

[samajammin]

Awesome! I'll look into this. Thank you both.