Reviewing Translations

All localized content on Learn WordPress should receive a translation review before it is published. Their reviewer should focus on these three areas:

  1. Is the language well-polished? (grammatically correct, no typos, etc.)
  2. Does the language follow the locale’s Glossaries and Style Guides?
  3. Does the translation follow the General Expectations for Translators?

If you know someone in the community who could review the content for you, feel free to connect with them directly and invite them to get involved. If you’re not sure who to ask, then a Translation Coordinator (Faculty Member) would be happy to discuss options with you.

Once chosen, please @-menton your content reviewer in the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue tracking your content creation. They are welcome to leave comments from their review directly in the GitHub issue. Having them participate in this way will help the Training Team recognize their contributions. (If you are unsure of their GitHub username, feel free to ask them for it in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Or, you can ask a Faculty Member to help you locate it.)

If you’re not sure who would be a good reviewer, an option may be to reach out to a Locale Manager of a given language to ask them who they think might be interested/available to help out. Each locale’s managers can be found by clicking on the respective “View Team Page” link from this list of Translation Teams.

When reaching out to Locale Managers, it’s a good idea to do so in the #polyglots Slack channel or on the Polyglots team blog. This keeps the conversation public, and others interested in helping out will be able to jump in, too.

Last updated: