Here with another yet another change of wind!
I’ve been following Docusaurus team’s PR about adding i18n support for Crowdin (l10n service) to docusaurus 2. It looks like the support has been recently merged but not yet included in the docs as it is in testing for release soon. The PR owner is offering onboarding to those interested
Good timing! I think we should test out a solution for multli-lingual tutorial with this Crowdin + Docusaurus 2 combo. Would you guys mind if I reached out to make this happen?
i18n (internationalization) = The structural components of a website that allow for multi-lingual content
l10n (localization) = The management of multi-lingual content itself.
Why Docusaurus 2 (i18n):
- It’s a static site framework designed explicitly for docs
- Tried and trusted: one of those Facebook products
- Now has i18n support with Crowdin integration
I tested Docusaurus out in past research for this project and rejected it because i18n was only available in the older Docusaurus 1 and felt it was not optimal for our use case. The new i18n support in Docusaurus 2 looks promising.
Why Crowdin (l10n):
I tested it out with our docs (see Crowdin repo here)
- Has a truly beautiful translation interface with machine aided translation
- Integration now supported with Docusarus 2
- Makes auto PR requests
- Translators can use their Github account with crowdin
- Translators can see very quickly which docs need translation attention
- Is not as buggy as Gitlocalize
- FREE for open source projects
As background, so far we’ve been experimenting with this Gatsby-based repo with Gitlocalize l10n. It’s an OK alterenative, but is just (poorly) reinventing the docusaurus wheel.
So what do you say - can I reach out on behalf of Redwood? Docusaurus 2 needs a case for private onboarding, and Crowdin requires I apply for an open source license with them.