Track the community's progress and join the discussion on Agrinet before the localized docs go live.
How language links work
Select a language to open its translation workspace in a new browser tab. Completed translations launch the localized Agrinet documentation, while in-progress efforts open the community hub for that language so you can follow along or volunteer.
The Contribute button mirrors this behavior, giving you a shortcut to jump straight into the translated experience without leaving the main Agrinet site.
Fully translated sites
These languages have complete translations. Enjoy the Agrinet docs in your language, review new changes, or help keep them aligned with the main site.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Translations in progress
These teams are actively translating new content. Follow their progress, offer feedback, and help review terminology before the localized Agrinet docs launch.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
Track the community's progress and join the discussion on Agrinet before the localized docs go live.
How to contribute
Each translation is maintained by volunteers. Contributions typically involve translating or reviewing Markdown files and opening pull requests in the repository for your language. Start by reading the contributor guidelines in that repository to learn how their team collaborates.
Not sure where to begin? Look for open issues labeled for newcomers, ask a question in the discussions tab, or offer to review a pending pull request. Every improvement helps the community access Agrinet documentation in their native language.
Start a new translation
Check the lists above to confirm your language isn't already in motion. When you're ready to propose a new translation, submit a pull request that introduces your language code, maintainer details, and repository location. Our team will review it and help you get listed on this page.
Maintainer responsibilities
- Sync with main docs: Keep your translation repository updated whenever new Agrinet content is published so readers always see current guidance.
- Review contributions: Provide timely feedback on pull requests, validate technical accuracy, and ensure terminology stays consistent across the site.
- Coordinate volunteers: Share progress updates, curate issues for newcomers, and celebrate milestones with your language community.
Locale readiness plan
- Run
node tools/translations/bootstrap-locales.mjsto extract fresh string catalogs for each configured locale. Review the internationalization overview and step-by-step tutorial so your team knows which JSON and Markdown files to translate before committing them under i18n/. - Translate the generated content manually or by connecting your workspace through the Crowdin integration guide. Keep terminology aligned with the Agrinet glossary before submitting pull requests.
- Verify every language renders by running
node tools/translations/build-locales.mjsand publish the resulting build/<locale>/ directories using the i18n Git workflow. This prevents 404s on routes such as /fr/ and keeps deployments in sync.
Resources
- Agrinet translation guidelines and scripts: Tools for syncing content, automating glossary checks, and preparing release updates.
- Docusaurus internationalization references:
- react-i18next: A popular React internationalization library that supports language detection, namespaces, and lazy loading for complex translation workflows.