Theme & Plugin Directories

Every Rosetta site now gets a theme and plugin directory for free! This is a new feature that has been rolled out to all Rosetta sites and is part of the site setup process for new locales. There are a number of features that need to be added to these directories to make them more friendly to localized visitors (for example, prioritizing translated themes and plugins over English ones), but the process has started.

How to Translate the Theme & Plugin Directories How to Translate the Theme & Plugin Directories

Translating all “meta” projects (Rosetta sites, etc) can be done from the Meta tab for your locale. You can track the progress of translating both the theme and plugin directories from their respective project pages. Once they’re translated, they will be deployed every 24 hours.

Top ↑

Translating Themes & Plugins Translating Themes & Plugins

The eventual goal is to be able to translate any theme or plugin in the theme and plugin directories. There are still a few things left to get to that point, but we’re well on our way and expect to turn on this feature soon. Once turned on, you’ll be able to translate any active theme or plugin! At the same time, you’ll be able to translate every theme and plugin. This can be a daunting experience, but we’re working on improving it.

For starters, some themes and plugins have their own, existing communities that are not hosted on If a theme or plugin developer requests it, we strongly recommend that the translation editor adds new, project-specific translation editors.

Example: if the author of the Twenty Fourteen theme (!) has an existing German translation editor in their community, they can request that the current German translation editors on (“Editors”) add their translation editor to the team, specifically for the Twenty Fourteen project.

Note: Want to understand how roles and permissions work? The Roles and Capabilities page walks through the different roles.

Translating 30,000+ plugins and 3,000+ themes is a very big task. Whenever possible, bringing in translation editors – for specific themes or plugins – is the ideal path and the polyglots team will work with Editors of all locales to make this happen.

Requesting New Translation Editors Requesting New Translation Editors

Should a theme or plugin author wish to migrate their translation editors (PTE) to, they should create a post on make/polyglots with the details.

You can see an example of a request post on the PTE Request page.

Where applicable, we recommend that a plugin author joins concurrent requests several plugins/themes and/or for several languages in the same request. However, importing plugins will happen in stages so that duplicate posts may be needed. The post must include usernames.

For additional requests to add more translation editors, you may edit your own recent post instead of creating a new request. If a longer time has passed, then it’s better to write a new post.

Top ↑

Cross-Locale Project Translation Editor Cross-Locale Project Translation Editor

A Cross-Locale Project Translation Editor (CLPTE) is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localise their product. The cross-locale project translation editor can import/validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors.

Top ↑

Criteria for a Cross-Locale Project Translation Editor Criteria for a Cross-Locale Project Translation Editor

To be granted access to import/validate strings for more than one locale, an organisation/plugin/theme author must cover the following criteria:

  1. Make sure that the translators they hire use the community style guides and glossaries, or create ones based on them and provide public links.
  2. Create a new account for this role rather than using a personal one, and fill in the profile page with contact information so that the local translation team can get a hold of them.
  3. Disclose the sources of translation (e.g. translation vendor) and reviewers (.org username) on the description of the new account
  4. List steps for other .org community volunteers to get involved in the review process
  5. Have a Slack account on and provide notice to the General Translation Editors of each locale after imports.
  6. Update their name with a (CL PTE)