• My first contribution to WordPress was not a big one: a few dozen short strings in the block editor.

    What I did

    I’m part of the Polyglots team, and my project is translating Gutenberg (the block editor) into Spanish (Costa Rica) “es_CR”, on https://translate.wordpress.org/locale/es-cr/default/wp-plugins/gutenberg/. For my first contribution I filtered the project by *Untranslated* and started working through the list.

    The strings were small but varied: UI labels like “Saving…”, “Box Control” and “Image size presets”, position names like “Top Right” and “Center Left”, and longer messages such as the error shown when a site doesn’t support a block.

    What I learned from the actual work

    Before translating, I read the Polyglots Handbook and the es_CR glossary. That reading paid off right away:

    Consistency matters more than creativity. In WordPress Spanish, a “post” is an *entrada*, so “Post Link” becomes “Enlace de la entrada” and “Post Comment” becomes “Publicar comentario”. I wasn’t translating word by word; I was matching what users already see across the rest of WordPress.

    Placeholders are untouchable. Strings like `%s`, `%d` or `%1$d of %2$d` and HTML tags like `<mark>` have to stay exactly as they are. Breaking one would break the interface for real users, so I double-checked every string that had them.

    How it connects to my work

    As a software engineer I’ve seen the other side of this: a confusing label or an inconsistent term in an admin screen slows people down and generates support tickets. Translating the editor made me think about interface text the same way I think about code: it needs to be consistent, tested in context, and reviewed by someone else before it ships.

    What’s next

    My goal is still at least 300 approved strings. Now that I know the workflow, I’m going to keep translating, follow up on review feedback from the es_CR team, and share my progress in the Halfway Check-In post.

  • The team: Polyglots

    I joined Polyglots, the team that translates WordPress, its plugins and its themes so people can use them in their own language.

    WordPress runs a huge part of the web, but for many people the experience only feels “theirs” when the interface speaks their language and uses the words they actually use.

    Why Polyglots ?

    I considered other options first. I looked at translating the Responsive theme and also at the Contributor Toolkit, but I dropped both. In the end, Polyglots made sense for two reasons:

    1. It’s a contribution I can make well from day one, I’m a native Spanish speaker from Costa Rica, and Spanish (Costa Rica), “es_CR”, is a locale with plenty of work still pending.
    2. It connects with what I do every day. I’m a software engineer, and a lot of my work involves websites and content platforms. I know how much a confusing label or a bad translation in an admin screen can slow someone down.

    My project: translating Gutenberg into es_CR

    My project is translating the Gutenberg plugin (the block editor) into Spanish (Costa Rica) on translate.wordpress.org. When I checked the es_CR translation was only about 50% complete, with more than 2,000 strings untranslated.

    My goal is at least 300 approved strings

  • For the first stage of the WP Credits program, I created my own personal website with WordPress. I hosted it on WordPress.com, which takes care of hosting and installation for me. I chose this option because it let me get the site online quickly, without worrying about servers, technical setup, or hosting costs. Since I work in software engineering, I was tempted to set it up myself with WordPress.org, but at this stage I preferred to focus on learning how WordPress works rather than on infrastructure.