Skip to content
HyperDAF editorialCommunity & Events

How WordPress Translation Teams Work (and How to Join)

The first time I saw WordPress in French, I actually gasped. I had been using it in English for two years — struggling through settings pages, guessing what buttons meant,…

Community & EventsEditor-curated guide
14 min8 sectionsIntermediate
Before you beginWhat this guide gives you
8Focused sections14Minutes to finishIntermediateExperience level52Article views
Start reading
Table of contents8

The first time I saw WordPress in French, I actually gasped. I had been using it in English for two years — struggling through settings pages, guessing what buttons meant, keeping a browser tab open to translate error messages. Then a friend showed me I could switch the whole dashboard to French. Every menu, every button, every explanation — suddenly in my own language. I sat there for ten minutes just clicking through menus I had never fully understood, feeling like someone had turned the lights on.

I am Amélie Dubois, and that moment changed my relationship with WordPress completely. I went from a nervous user to a contributor: I joined the French translation team, and over the past four years I have helped translate thousands of strings — the small pieces of text that make up the WordPress interface. I am not a developer. I had never contributed to open source before. I just spoke French and wanted to help.

Maybe you have felt what I felt — using software in a language that is not quite yours, doing mental translation with every click. Or maybe you are fluent in two languages and never realized that skill alone qualifies you to contribute to the world’s most popular website platform. In this guide, I will show you exactly how WordPress translation teams work, what the experience is really like, and the step-by-step path to joining one yourself. No coding. No experience required. Just your language.

Whether you speak Urdu, Spanish, Hindi, Portuguese, or any of the hundreds of languages WordPress supports, there is a team waiting for you. Let us find it.

Illustration of translating WordPress into many languages

Quick trust note before we begin: everything here comes from my own four years inside the translation community. I am not quoting a handbook — I am telling you what actually happens, including the parts that confused me at first.

Here is what this guide covers:

  • What WordPress Translation Teams Actually Do
  • The Polyglots Community: How It Is Organized
  • What Translating Looks Like Day to Day
  • How to Join a Translation Team (Step by Step)
  • Your First Translation: What to Expect
  • Growing From Contributor to Team Member
  • Frequently Asked Questions
  • Final Thoughts

Ready? Your language needs you. Let us begin.

What WordPress Translation Teams Actually Do

Here is the simple version: every piece of text you see in WordPress — “Publish,” “Add New Post,” “Are you sure you want to delete this?” — exists in a master list of short text pieces called strings. Translation teams take each English string and write its equivalent in their language. That is the whole job. No code, no design, no meetings about strategy. Just language.

But do not let the simplicity fool you. This work is enormous in scale and enormous in impact. WordPress core alone has thousands of strings. Then there are the default themes, the default plugins, and — this is the big one — the tens of thousands of plugins and themes in the directory, each with their own strings waiting for translation. When a translation team finishes a language, millions of people can suddenly use WordPress comfortably. Your few hours of translating can change the daily experience of people you will never meet.

I think of it like this: developers build the house, but translators make it feel like home for everyone. A farmer in rural France, a teacher in Senegal, a shop owner in Quebec — they all get to use professional website software in the language they think in. That only happens because volunteers like you and me sat down and translated “Settings” and “Save Changes” and ten thousand other small phrases.

Here is the deal: you do not need to be a professional translator. You need to be fluent in two languages and care about getting the meaning right. Some of the best contributors I know are teachers, students, and retirees — people who simply love their language and want WordPress to speak it well.

The Polyglots Community: How It Is Organized

The translation community has a name: Polyglots. It is one of WordPress’s official contributor teams, and it is organized by language — there is a French team, an Urdu team, a Spanish team, a Japanese team, and dozens more, each working independently on their own language.

Each team has a simple structure. At the top are the General Translation Editors (GTEs) — experienced volunteers who review and approve translations for their language. They are the quality gate: nothing goes live until a GTE approves it. Below them are the Project Translation Editors (PTEs) who manage specific projects, and then the contributors — people like you and me — who suggest translations. When I started, I was a contributor suggesting translations. A GTE reviewed my work, approved the good ones, and corrected me when I got the tone wrong. That feedback loop is how you learn.

Teams communicate in their own spaces — usually a Slack channel for the language, plus a team page on the WordPress.org Polyglots site. The French team, for example, has regular informal discussions about tricky translations: should “widget” stay in English or become “gadget”? Is there a French word for “slug” that actual users understand? These debates are my favorite part. Language is alive, and the team treats it that way.

Note: You do not need anyone’s permission to start suggesting translations. The system is open — you create an account, pick your language, and start. Approvals come later, from the GTEs. The barrier to entry is genuinely zero, which is rare and wonderful.

Illustration of the global WordPress Polyglots volunteer community

What Translating Looks Like Day to Day

Let me walk you through what I actually do on a typical translating evening, so you can picture it.

I open GlotPress — the web-based translation tool WordPress uses. No installation, no setup; it runs in the browser. I pick a project (say, the latest WordPress release or a popular plugin), filter for untranslated strings in French, and start working through the list. Each string shows the English original, any existing translation suggestions, and a box where I type mine.

A string might be something like “Search results for: %s” — and my job is to write the natural French equivalent, keeping the %s placeholder (which the software replaces with the search term) in the right place. Some strings take five seconds. Some take five minutes, because the English is ambiguous and I need to check where the string actually appears in the software to understand the context. GlotPress shows you context clues — which file the string comes from, sometimes a comment from the developer. When context is missing, I open a test site and find the string in the interface. This detective work is oddly satisfying.

I usually translate for about an hour, maybe thirty to fifty strings. Then I stop. There is no quota, no deadline, no manager. Some weeks I do three evenings; some months I do nothing at all. The work waits patiently. That flexibility is why so many busy people can contribute — it fits around real life instead of demanding a schedule.

The best part? A few weeks later, I update a WordPress site and see my translations live in the dashboard. My words, in software used by millions. It never gets old. The first time it happened, I called my mother to tell her. She did not quite understand, but she was proud anyway.

How to Join a Translation Team (Step by Step)

Enough background — here is the exact path, step by step. I have walked three friends through this, and it takes about twenty minutes.

Step 1: Create a WordPress.org account. Go to wordpress.org and register. This one account works everywhere — the forums, GlotPress, Slack, all of it. Use a real name or a consistent nickname; the community values real humans.

Step 2: Find your language team. Visit the Polyglots teams page (wordpress.org/polyglots/teams/) and find your language. Each team page shows its GTEs, its Slack channel, and its current translation progress. Read the team’s page — some teams have style guides or glossaries (agreed translations for tricky terms) that you should know about before starting.

Step 3: Join the team’s Slack channel. WordPress has a community Slack (chat.wordpress.org), and each language team has its own channel. Introduce yourself briefly: your name, your language background, that you want to help translate. Teams LOVE new contributors — you will be welcomed. Ask if there is a glossary or style guide to read first.

Step 4: Open GlotPress and start suggesting. Go to translate.wordpress.org, select your language, pick a project with untranslated strings, and start suggesting translations. Begin with WordPress core or a plugin you actually use — familiarity with the software helps you translate accurately.

Step 5: Be patient with approvals. Your suggestions go into a queue for GTE review. Depending on the team’s size and activity, approval can take days or weeks. Do not take slow approvals personally — GTEs are volunteers too. Keep suggesting; when approvals come, read the feedback carefully, especially corrections. That is your real training.

Illustration of the step-by-step path to joining a translation team

Bonus Tip: Start with a plugin you use every day. You already know what every button does and where every message appears — that context makes your translations naturally accurate. Translating software you have never used is much harder, because you are guessing at meaning instead of knowing it.

Your First Translation: What to Expect

Let me set honest expectations, because the first session surprises people.

It is slower than you think. Your first ten strings might take thirty minutes. You will second-guess every choice: Is this the right register — formal or informal? Should this technical term stay in English? What did the team decide last time for this word? This is normal. Speed comes with familiarity — with the tool, with the team’s conventions, with the software’s vocabulary. By your fifth session, you will be three times faster.

You will make mistakes, and that is the system working. I once translated “post” (as in blog post) using the French word for a fence post. A GTE caught it, corrected it gently, and I never made that mistake again. The review system exists precisely so beginners can contribute safely. Every correction is a free lesson. The only real mistake is not starting.

Consistency matters more than perfection. Teams care most that the same English term gets the same translation everywhere. If “dashboard” becomes “tableau de bord” in one place and “panneau de contrôle” in another, users get confused. This is why glossaries exist — check the team’s agreed terms before translating, especially for common words. When in doubt, look at how similar strings were already translated and match the pattern.

You will develop opinions about language. This surprised me most. After a year of translating, I had strong feelings about whether French software should say “téléverser” or “uploader,” and I would defend them passionately in team discussions. Translation work makes you think about your own language in ways nothing else does. It is intellectual work disguised as volunteer work, and it is genuinely enriching.

Something I have noticed across the community: the teams that produce the best translations are the ones where contributors care about the end user — the real person reading the interface. Keep that person in mind. A teacher in Dakar, a grandmother in Lyon. Write for them, not for the dictionary. And if you ever build products for a global audience yourself, this instinct becomes gold. I have seen it firsthand: at HyperDAF, our development team builds WordPress products from scratch with a worldwide audience in mind from day one — clean code that works in every language, no shortcuts. Their marketplace of the team’s own themes, plugins and tools launches very soon at hyperdaf.com.

Growing From Contributor to Team Member

Suggesting translations is the beginning, not the ceiling. Here is where the path leads if you stick with it.

After months of consistent, quality suggestions, GTEs notice. The natural next step is becoming a Project Translation Editor for a specific plugin or theme — meaning your translations for that project go live without waiting for review. It is a vote of confidence, and it feels wonderful. From there, some contributors become GTEs themselves, taking responsibility for an entire language. The French team members who reviewed my early work? Two of them started exactly where I did — as nervous beginners suggesting their first strings.

Beyond translation itself, the Polyglots community opens doors to the wider WordPress world. Translators are invited to contributor days at WordCamps (I will talk more about community events in a moment), and translation work counts as genuine open-source contribution — the kind you can put on a CV with pride. “I help translate WordPress into French” has started more interesting conversations for me than any job title ever did.

But honestly? The deepest reward is quieter. Every time I see a French user navigate WordPress confidently — no guessing, no translating in their head — I know my evenings made that possible. You cannot buy that feeling. If you have ever wanted to contribute to something bigger than yourself but thought open source was “for developers,” this is your invitation. It was never only for developers. It was always for people who care.

Illustration of growing from new contributor to experienced translator

Frequently Asked Questions

Do I need to know how to code? Not at all. Translation happens in GlotPress, a web tool — you read English, you write your language, you click save. I have translated thousands of strings and written exactly zero lines of code. If you can use a web form, you can translate.

What if my language already has 100% translation? First, check — “100%” usually refers to WordPress core, but thousands of plugins and themes still need your language. Second, translations need maintenance: every WordPress release adds new strings, and old translations need review as language evolves. There is always work. Always.

How much time does it take? As much as you want. There is no minimum, no commitment, no schedule. I do about two hours a week when I am active, and nothing for weeks when life is busy. The strings wait for you. This is volunteering on your terms.

Will my translations actually go live? Yes — after GTE review and approval, they ship in the next WordPress release or plugin update. Your name appears in the translation credits. Real software, real users, real impact. The pipeline from your suggestion to millions of screens is direct and real.

Can I translate themes and plugins too, or just WordPress core? Everything. Core, default themes, and any plugin or theme in the directory with translation support — which is most of them. Many contributors specialize: one person translates all the e-commerce plugins, another handles photography themes. Find your niche and own it.

Final Thoughts

I still remember that evening — clicking through a French dashboard for the first time, ten minutes of pure wonder, feeling like WordPress had finally learned to speak to me. What I did not know then was that behind every one of those French words was a volunteer. Someone who sat down after dinner, opened GlotPress, and decided that French speakers deserved better.

Now I am one of those someones. And you could be too.

Your language — whatever it is — has millions of potential WordPress users who would do better work, feel more confident, and enjoy the web more if the software spoke to them clearly. The only thing standing between them and that experience is people willing to translate. People like you, reading this sentence right now. For help between sessions, see where to get real WordPress help. If you like meeting contributors in person, read why every WordPress freelancer should attend a meetup. Translating themes is easier when you know how to buy a WordPress theme without getting burned. The plugins you translate are covered by WordPress plugin licenses explained before you buy. If you run your own site, read our guide to self-hosted WordPress.

So here is my challenge: this week, create that WordPress.org account, find your team, and suggest your first ten strings. Ten strings. Twenty minutes. That is all it takes to begin. Four years from now, you might be the GTE welcoming the next nervous beginner — telling them the same thing I am telling you: start, make mistakes, keep going. Your language needs you.

Have questions about joining, or want help finding your team? Leave a comment below — I answer every one, and I would love to welcome you aboard.

Written by

Amélie Dubois

Amélie crafts interfaces for WordPress products with a focus on clarity and accessibility. Her 7 years of design practice inform her articles on usability, typography, and conversion-focused layouts.

7 published articles
View all articles

Related articles

View all articles

2 comments

Join the discussion

Your email address will not be published. Required fields are marked *

Keep comments relevant and respectful.