Category: Reflexion

  • My WP Credits Final Report

    Hi everyone! I’m María, a Systems Engineering student in Costa Rica, and this is my final report for the WP Credits program. During the program I contributed to the WordPress Polyglots team by translating WordPress projects into Costa Rican Spanish (es_CR). This report summarizes what I worked on, the challenges I faced, and what I learned along the way.

    Teams and projects I contributed to

    I joined the Polyglots team, which works to make WordPress available in as many languages as possible. My goal was to help Spanish speakers in Costa Rica use WordPress in their own language. I worked on two translation projects:

    • Forums: the text of the WordPress support forums.
    • Gutenberg: the interface of the block editor.

    Learning resources

    I relied mainly on the Polyglots Handbook to understand how translating, reviewing, and approving strings works. I also studied existing approved translations in my locale to follow the same style and terminology. My mentor, Merlin Ulloa Matamoros, guided me throughout the process and answered my questions.

    Challenges and solutions

    1. Keeping terminology consistent. Many technical terms can be translated in more than one way. I solved this by checking the locale glossary and reviewing previously approved translations before submitting mine.
    2. Handling placeholders and code in strings. Some strings include variables and HTML tags that must stay intact for the interface to work. I learned to read each string carefully and double-check these elements before saving.
    3. Managing time during the semester. Translating hundreds of strings takes sustained effort. I handled it by working in short, regular sessions instead of leaving everything for the end.

    My contributions

    Key learnings from the WP Credits program

    • Open source contribution is a collaborative process: every translation goes through review, and that feedback makes the work better.
    • Small, consistent contributions add up. Hundreds of approved strings started with one translation at a time.
    • Good translation is about clarity for real users, not just word-for-word accuracy.

    New skills gained

    • Technical: working with the WordPress translation platform (GlotPress), following glossaries and style guides, and handling strings with placeholders and markup.
    • Soft skills: attention to detail, time management, and responding to community feedback.

    Personal reflections and next steps

    What I enjoyed most was knowing that my work will be used by real people every time they open the editor or the support forums in Spanish. After WP Credits, I plan to keep contributing to Polyglots and continue improving the es_CR translation

  • Reflection: Halfway Check-In

    What I’ve accomplished since my first post

    When I chose Polyglots, my goals were to learn the translation workflow, contribute a meaningful number of approved translations in both projects, and collaborate with the community. At the halfway point, I’m happy with my progress:

    • WordPress Forums: 61 translations approved.
    • Gutenberg: 362 translations approved (191 in Development and 171 in Stable), with 1 still pending review.

    Beyond the numbers, I now feel comfortable using the translation editor, following the glossary and style guide, and keeping placeholders intact.

    Obstacles and how I handled them

    The biggest obstacle was waiting for review. For a while my Gutenberg translations stayed as suggested, and it was hard to know if I was doing things right. I handled it by continuing to translate and by checking my work against the glossary and approved translations, so I kept consistent. Once they were approved, I knew the approach was working.

    The second obstacle was context. Many Gutenberg strings are short and technical, and the right wording depends on where they appear in the interface. I handled this by reading each string carefully, comparing similar strings, and choosing terms that stay consistent across the project.

    What’s still ahead

    Before wrap-up, I want to:

    • Keep contributing to Gutenberg and get my last pending suggestion approved.
    • Look for more strings to translate, or review work from other contributors.
    • Review my consistency with the es_CR glossary across both projects.
    • Talk with my mentor about how to keep growing in Polyglots.

    Where I expected to be vs. where I am

    I expected to have a smaller number of approved translations by this point. Having 61 approved in Forums and 362 in Gutenberg is further along than I expected, and the main difference is that I learned the workflow faster once I started translating instead of only reading the handbook.

    What would help most in the second half

    More feedback from reviewers and my mentor on the quality of my translations, so I can improve my wording and consistency.

  • Reflection: Your first contribution

    My First Contribution to Polyglots:

    Learning by Translating

    Reading the handbook for the first time

    Opening the Polyglots handbook for the first time felt like a lot of information at once. It covers how the translation editor works, how glossaries and style guides keep terminology consistent, and how translations move from suggested to approved. Once I started translating, the handbook made more sense, because I could connect each rule to a real string in front of me. The glossary and the style guide were the parts I kept coming back to.

    My first contribution

    I’m contributing to the Spanish (Costa Rica) locale, es_CR, in two projects:

    • WordPress Forums: 61 translations already approved.
    • Gutenberg: 362 translations approved (191 in Development and 171 in Stable), with 1 still pending review.

    I began with the Forums and then moved to Gutenberg, which has many more strings and more technical terms. Translating them showed me that the job is not word-for-word: I had to read each string in context, keep placeholders intact, and choose wording that sounds natural for Costa Rican Spanish while staying consistent with the glossary.

    How the team communicates and works

    Polyglots works through a review system: contributors suggest translations and editors approve them. That means quality and consistency matter as much as volume. At first my Gutenberg translations were waiting for review, and seeing them approved showed me the process works and that patience is part of the job. It also felt good to see my work reflected in the project.

    What surprised me most

    I didn’t expect how much translation depends on context and consistency. A single word can change depending on where it appears in the interface, and one inconsistent term can confuse users across the whole product.

    What’s next

    I’ll keep contributing to both projects and look for more strings to translate and review. One question I still have for my mentor is how I can make sure my translations stay consistent with the es_CR glossary and style guide, especially when a term has more than one possible translation.

  • Reflection: Choosing Your Team and Project

    Why I Chose Polyglots: Bringing WordPress to Costa Rican Spanish

    For my WP Credits contribution, I joined the Polyglots team, the group that translates WordPress into more than 200 languages. I’m working on the Spanish (Costa Rica) locale, es_CR, and my project has two parts:

    1. WordPress Forums (https://translate.wordpress.org/locale/es-cr/default/meta/forums/ ): translating the interface strings of the support forums, where many Spanish-speaking users go for help.
    2. Gutenberg (translate.wordpress.org/locale/es-cr/default/wp-plugins/gutenberg): translating the strings of the block editor plugin, which is how people build and edit content in WordPress today.

    What drew me to Polyglots

    I’m a Systems Engineering student in Costa Rica, and I use software in both English and Spanish every day. I know how much easier a tool is to use when the interface speaks your language, especially for people who are just starting out. Translation is also a way to contribute without being an expert developer: every string I translate is something a real user will read.

    Why these two projects

    The forums are where users ask for help, so clear translations there lower the barrier for people who don’t speak English. Gutenberg is the editor people use constantly, so every translated string is seen by a lot of users. Together, they let me work on both support and daily use.

    How this connects to my skills

    My studies have given me a technical vocabulary and the habit of reading software documentation carefully. Translating UI strings uses both: I have to understand what each string does in context and choose wording that is accurate, consistent, and natural for Costa Rican Spanish.

    What I hope to learn and achieve

    • Learn how the Polyglots workflow works: translation editors, glossaries, style guides, and the review process.
    • Contribute a meaningful number of approved translations in both projects.
    • Practice collaborating with an open-source community and receiving feedback from reviewers.
    • Come back to this post later and check whether this is still the right fit for me.
  • Reflection: Building your personal website

    This is my first personal website. I decided to use WordPress.com because it was recommended by my university as part of the WP Credits Program.
    ​One of the challenges I faced was understanding how WordPress creates pages, posts, and navigation. At first, some of the content I created was not showing up where I expected. So, I had to explore the settings and re-watch the Beginner WordPress User course to understand how it works.
    ​I have to be honest: I thought WordPress was easy to start using, but I was wrong. It takes some practice to understand all the options and customize the site the way I want.