Starting a New Translation
This page lists the steps to take to create a a new Gatsbyjs.org translation.
Before requesting a new translation, make sure to read the maintainer responsibilities to affirm that you accept the responsibilities of being a translation maintainer.
Before creating a new issue, make sure to check the list of open translation requests. If one already exists for your language, ask to be added to the list of maintainers there.
If you don’t see the language among the issues listed, feel free to create a new translation request issue for it and follow the instructions.
For a new translation, open an issue with information about your intended language. If you already have co-contributors to act as fellow code owners and provide checks and balances for PR reviews and quality assurance, that would be very helpful! Otherwise, you can check out other translation request issues people have made and offer to join, or get in touch with us at Gatsby for help in building your translation team.
The Gatsby team will choose to approve a translation request based on the following criteria:
- Are there at least two maintainers listed?
- Do at least one of the maintainers have previous open-source experience and experience working with GitHub and git?
- Are the maintainers fluent speakers? Maintainers do not need to have experience translating, but must be fluent enough in the language to be able to translate technical writing.
Once the translation request is approved, a member of the gatsby team will run the an automated script to create your repository and set everything up.
At this point, you and your co-maintainers should read the rest of the maintainer guide for more information on how to manage your translation repository. You can also check out the translation contributor guide for information on contributing translations to your own repo, and start working on your translation style guide.
Edit this page on GitHub