WordPress 4.6 is coming on August 16th and the week of, and after, a release, are usually busy times for us here on make/polyglots, as we’re trying to get the new strings A string is a translatable part of the software. A translation consists of a multitude of localized strings. to as many people as possible.
These are also the periods where more new contributors are drawn to the project and documentation comes in handy.
That’s why I’d like to organise two August polyglots documentation sprints with two main goals:
- Clean old, irrelevant content from the handbook at https://make.wordpress.org/polyglots/handbook/
- Check for incorrect information
- Check for outdated information that’s no longer irrelevant
- Replace old screenshots with new ones where UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing./design has changed
- Test for focus groups and figure out what content we’re missing for our main target groups:
- New translation contributors
- Getting started
- Registering an account
- Working with translate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.
- Understanding the contributor hierarchy (roles)
- Finding local glossary/style guide
- Getting in touch with GTEs
- Translation Editors Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles:
General Translation Editor and Project Translation Editor and General Translation Editors
- Requesting a new locale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/
- Inactive translations/ becoming a GTE A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale.
- GTE responsibilities and requirements
- Creating a Glossary and Style guide
- Working with translate.wordpress.org
- Adding other GTEs/PTEs
- Working with WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
- Releasing translation
- Manually releasing translations
- Automatic language packs
- Rosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. site maintainers
- Translating the interface
- Setting up basic pages
- Localized Plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and Theme Directories
- Showcase – how to and best practices, also rules and examples
- Creating content for the Blog – ideas for different types of content and examples
- Adding a “Get involved” page – (template + examples)
- Local support forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. moderators
- General expectations
- Translating the interface
- Adding new moderators
- Plugin/theme authors wondering how to get their project successfully localized on translate.wordpress.org
- Requesting translations for their projects
- Requesting Project translation editors
- Translation options for plugin authors – import vs using community translations
- Cross locale PTEs
- Releasing translations (language packs)
- Working with the translation community
If someone would like to get involved with working on these tasks and adding / updating content for current pages (here’s the updated Content spreadsheet), please say so in the comments so we can plan the sprint.