Recap: Content Localization Foundations Project


The Training Team’s efforts have historically been focused on creating content for in the English language. The Content Localization Foundations project was the team’s first efforts to onboard contributors who speak other languages and translate content into different locales.

Over the course of 5 months, 28 volunteers created 36 pieces of localized content across 10 locales. Additionally, volunteers translated some of the Training Team’s handbook pages related to content translation into 5 locales.

The project achieved some of the objectives initially laid out. Many points were learned that would improve the entry to localizing content on The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. Some necessary changes for the Locale Ambassador role were also identified. The team will continue to iterate on content localization processes to respond to these findings.

Project Achievements

The following are what this project achieved in its six month duration from November 2022 to April 2023.

Content Translation

Goal: Translate 10 priority learning content into each target language (Inclusive of Lesson Plans, and Tutorials)

Completed: The team translated the following pieces of content:

LocalePublished contentTranslations waiting reviewTranslated handbook pagesProject contributors
Arabic1 Lesson Plan2
French1 Tutorial22
Greek9 Tutorials2
Gujarati4 Lesson Plans, 1 Tutorial145
Hindi6 Lesson Plans24
Indonesian1 Lesson Plan, 2 Tutorial3
Italian2 Lesson Plans1 Lesson Plan53
Japanese1 Online Workshop3
Khmer1 Lesson Plan1
Tamil6 Lesson Plans23
Total20 Lesson Plans,
4 Tutorials,
1 Online Workshop
2 Lesson Plans, 9 Tutorials2528
Number of content translated, by locale

Learnings: The project wasn’t able to translate 10 pieces of content in any one language.

Part way through, the project recognized the process of translating a Tutorial (recording and editing a video) was more involved than most translators were able to contribute to. The project changed priorities to translating Tutorial subtitles instead, but not early enough to reach the goal of “10 pieces of translated content” in any locale.

Next steps: Continue translating content in different locales, but focus on text-based content as a priority.

Onboarding and Documentation

Goal: Create a workflow of onboarding and how-to guides that take folks through the journey of joining the Training Team to publishing localized content

Completed: The team published a Content Translator onboarding path within the general Getting Started onboarding program. We now also have multiple resources in the handbook about publishing localized content, including Content Localization, Translating Subtitles, and Locale Ambassador.

Learnings: Feedback was provided on how it was difficult for many contributors to track translation items in 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. amongst other content creation issues.

Additionally, we received mixed feedback regarding using GitHub to manage translations. In general, those with experience using GitHub found the documented processes easy to follow. At the same time, others with little/no experience using GitHub showed hesitation to getting involved. 

Next steps: To make tracking issues easier, we can move content localization issues into their own GitHub project board.

As for the perceived difficulties of GitHub itself, we can either improve the current onboarding to provide more assistance, or the team can consider using a different tool to manage translations (such as translation plugins, or Computer Assisted Translation tools). This is something the team will investigate further.

Goal: Bring in at least two new Training Team Members from the following locale communities: Spanish, Japanese, German, French, and Italian

Results: The project had 28 contributors across 10 locales that contributed to publishing content.

Learnings: The project was able to bring in project contributors from 3 of the 5 most used WordPress locales. WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia was a good onboarding opportunity, where we saw multiple contributors from other locales join the project. Many contributors joined either through the Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus. event or after hearing a presentation from @bsanevans on the Training Team’s localization efforts. (View slides here.)

Next steps: These results encourage the Training Team to continue having a presence at different events – especially WordCamps and Contributor Days – where the team can present the need for content localization to different communities.

Enlisting Locale Ambassadors

Goal: Establish the Locale Ambassador role. Enlist at least five Locale Ambassadors.

Completed: The Locale Ambassador handbook page was published. 6 contributors (in 5 locales) volunteered to be Locale Ambassadors for this project. Of these, 2 locales were able to publish content.

Notably, @piermario and @margheweb did a fantastic job as Italian Locale Ambassadors. They actively onboarded contributors and translation reviewers. They also represented the Training Team at Contributor Day at WordCamp Torino, leading a table focused on translating content for 

Learnings: The project received the following feedback about the Locale Ambassador role:

  • Some are hesitant at joining the role as its definition includes a broad range of responsibilities. (​​A Locale Ambassador is someone who bridges their local community and the Training Team through various initiatives such as, but not limited to: bringing contributors into the Training Team, onboarding contributors to the Training Team’s processes and providing language support, creating localized content.)
  • Some would become a Locale Ambassador if they weren’t alone in the role in their locale.
  • Currently, Locale Ambassadors continue to rely on Faculty Administrators to triage GitHub issues or provide translators with website access, causing a bottleneck in the translation process.

Next steps: The project suggests renewing the Locale Ambassador role in the following ways:

  • Renaming the role to “Translation Coordinators” to better describe the main focus of the role.
  • Positioning “Translation Coordinators” as a fifth role in the Faculty Program.
    • While this adds a vetting process to joining the role, it will provide the role with the same GitHub/website access as Faculty Administrators, empowering them to conduct the various tasks that currently rely on an Administrator to perform.
    • It will also connect Translation Coordinators with others already in the Faculty program, providing better support.

Website Development

Goal: Enable locale tagging for Courses, Tutorials, and Online Workshops


Goal: Have localized content show first on the Learn WordPress homepage when someone visits the page in their native locale

Completed: Localized Tutorials show on the homepage when viewed in a locale that has one.

Next steps

While this project will now be closed, the need to localize content on Learn.​​ continues. The project suggests the Training Team continue to iterate on the content localization process, starting with these points:

  • Renew the Locale Ambassador role as a fifth Faculty role: “Translation Coordinators”.
  • Focus localization efforts on text-based content.
  • Create a dedicated project board within the team’s GitHub repository to track content localization.
  • Continue raising awareness of the localization needs of at events.

Thank you to the following contributors who were involved in publishing localized content during this project: @piyopiyofox @webtechpooja @nadaelsharkawy @jdy68 @wplmillet @eboxnet @kosakkas @sagarladani @vanpariyar @baroliyamayur @amitpatelmd @viralmehta @piyushmultidots @pitamdey @askaryabbas @piermario @lidialab @margheweb @ardianimaya @kharisblank @fikekomala @megane9988 @vannkorn @karthickmurugan @dhanendran @kaderibrahim Aymenboch

Thanks also to @webtechpooja @courtneypk @meaganhanes who contributed to this post.