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.
