WordPress Polyglots Team can translate practically everything that is available on the official WordPress project websites if they wish to do so, including but not limited to:
- Products
- WordPress software (core)
- Plugins/themes on WordPress.org directory
- Mobile apps
- Website UI
- Rosetta site (localized WordPress.org, e.g. fr.wordpress.org)
- WordCamp.org
- Support forums
- Website contents
- Support documentation (user manual)
- WordPress.org news blog & some pages
- Make WordPress announcements and other highlights
- Make WordPress handbooks for contributors
- Other
Deciding on what to translate
Very often, Polyglots Team contributors start translating because they want to use WordPress itself or a plugin/theme in their language. After they finish translating the projects for themselves, they ask – what should I translate next?
The answer really depends on what the contributor is trying to accomplish through their contribution and the translation status of their locale. For those who just want to help the WordPress project with translating anything, here is a list of priority projects and contents:
- WordPress Core
- The latest bundled theme (Twenty XX)
- Highly visible page(s) on localized site (e.g. front page, about page)
- Get involved page (teams create their own version)
Also, it’s highly recommended to invest some time in content that can help grow your translation team. You can start by documenting the translation process in your language, then build a style guide/glossary (these are covered later in this course). Remember, you can only translate a limited amount of strings alone. By inviting more people to your team, you can build a community of contributors to share each other’s work with.
If you’re still not sure where to go next, you can decide based on the impact and effort required. Below is a rough prioritization of various translation projects, based on their importance and the number of strings.
