Tuesday Trainings: How to Translate Community Team Resources

This year we’ve changed the format of Tuesday Trainings to better get directly at the issues that seem to be on the minds of folks in our community. How are we doing that? Great question. We’re either seeking to answer commonly asked questions or address commonly heard complaints, concerns, and confusions.

If there’s a question you’d like to see answered or a topic you’d like to see discussed, please share it in the comments or email me at support@wordcamp.org with the subject line Tuesday Trainings. Now onto this week’s topic.

This week’s question: How can I contribute to the Community Team as a translator?

As a non-English speaker, have you ever thought, “I wish this information were available in my language” when you are reading something published by Community Team contributors?

If you find any information that is likely to be valuable to your local community, we invite you to help us share the knowledge by translating it.

Before getting started, be sure to get in touch with others in the local community and work together.

You can join their language or region-based Slack workspace, or ask around in Make WordPress 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/. #polyglots channel.

Choose what to translate

While it’s up to you to decide where to get started, here are some of the commonly translated contents:

Recommended contents to translate

If you don’t have any preference for the contents to translate, you can start from these recommended contents.

MeetupMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. Basics

These are the WordPress Meetup Chapter Program basics and are likely to stay relevant for a long time.

Virtual Event Resources

If you see a lot of confusion in your community with the transition to online events, it’s a good idea to provide translated information for reference. Please note these pages may change more often than others, as the Community Team updates the online event guidelines to adopt the community’s needs.

Where/How to publish the translation


Generally speaking, the Team P2 or the Handbook section on your locale team’s Rosetta site are great places to publish community team contents.

Some teams may decide to use their Rosetta site blog or page. There is no strict rule for where to publish the translated contents, as long as they are part of WordPress open-source properties (e.g., on a wordpress.orgWordPress.org 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. https://wordpress.org/ subdomain site). It’s a good idea to discuss the best way with the Polyglots team members of your locale.

If you are unsure how to contact the existing team or set up the Rosetta site, please ask in the #polyglots channel in the Make WordPress Slack.

WordCamp.org site interface and contents

You can translate the UIUI 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. text of the WordCamp.org site on translate.wordpress.org. For more information about the translation platform, visit the First Steps page of the Polyglots Handbook.

If you are interested in translating the contents of a 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. site, find a contact form on the site and offer to help. Optionally, you can ask in #community-team to get connected with the organizing team.

This post was written as a result of the Documentation Editing Sprint. Thanks @mpcdigital for reviewing and @harishanker for organizing the sprint!