My First Contribution to Polyglots: From Theory to Practice

Date: July 24, 2026
Estimated reading time: 4 minutes

After completing the induction and choosing Polyglots as my contribution area, it was time to make my first contribution. Up to that point, I had learned about the general structure of the community, the available tools, and some of the recommendations for translating content within WordPress.

However, moving from explanation to practice was different. It was no longer only about understanding the purpose of the team, but about entering the platform, reviewing real strings, and suggesting translations that would later be evaluated by other members of the community.

This first experience helped me better understand what working in Polyglots involves and which aspects I needed to consider before submitting a translation.

My first experience with the platform

To begin, I accessed the WordPress translation platform and looked for the project where I would make my contributions. I then selected Spanish for Costa Rica, identified as es_CR.

Within the Astra project, I found different English strings that still needed translation suggestions. Before choosing one, I reviewed several options to identify a string whose meaning I could understand clearly enough.

When I selected a string, the platform displayed the original text, a space to enter the translation, and, in some cases, additional information about the context. This context was important because a word can be translated in different ways depending on whether it appears in a plugin, a page, or a button.

Procedure followed

To make my first contribution, I followed these steps:

  • I logged in to my WordPress.org account.
  • I accessed the translation area.
  • I selected the assigned theme.
  • I chose Spanish for Costa Rica, es_CR.
  • I reviewed the strings that were waiting to be translated.
  • I selected a string whose context I could understand.
  • I analyzed the meaning of the original text.
  • I wrote a suggestion that sounded clear and natural in Spanish.
  • I reviewed the spelling, punctuation, and technical elements.
  • I submitted the translation so that it would remain pending review.

For my first contribution, I analyzed the original text and wrote a suggestion that preserved its meaning while also sounding natural in Spanish.

Obstacles encountered

One of the first difficulties was the lack of context in some strings. Although I could understand each word separately, it was not always clear where the message would appear in the interface or what its function would be.

I also had questions about certain technological terms. Some words can remain in English, while others have a translation recommended by the community. For this reason, it was not enough to choose the first equivalent I found; I needed to check whether the term was already being used in a specific way within WordPress.

Another aspect that required attention was the presence of variables, symbols, or tags. These elements are part of the system’s functionality and must not be accidentally removed or modified during translation.

In addition, because this was my first contribution, I reviewed the suggestion several times before submitting it. Although this made the process slower, it also helped me feel more confident about the result.

The review process

After submitting the translation, it remained pending review. I understood that suggesting a string does not mean it is published automatically, since it must first be evaluated by someone with the appropriate permissions within the team.

At first, I felt some uncertainty because I did not know how long the review would take or whether my suggestion would be accepted. However, I understood that this process is necessary to maintain the quality and consistency of the translations.

The review process also provides a learning opportunity. When a suggestion requires changes, the feedback helps contributors better understand the criteria used by the community and avoid similar mistakes in future contributions.

What I learned

This first experience helped me understand that translating in Polyglots requires taking the time to analyze each string before writing a suggestion. It is not about translating word by word, but about finding an expression that preserves the meaning and is easy for users to understand.

I also learned to pay closer attention to the context, technical terms, and elements that must remain unchanged. Even when a string is short, every detail can affect the quality of the translation.

Another important lesson was understanding that contributions are part of a collaborative process. My role was to suggest a translation, while other people were responsible for reviewing it and confirming that it met the established criteria.

Personal reflection

Making my first contribution gave me a mixture of excitement and nervousness. On one hand, I was happy to begin participating in the community in a real way. On the other hand, I had doubts about whether I had interpreted the string correctly and whether my suggestion would be approved.

Although it was a small activity, it represented an important step in the project. It helped me overcome my initial uncertainty and better understand the procedure I needed to follow in order to continue translating.

After this first experience, I felt more confident about reviewing new strings. My next goal was to apply what I had learned, pay closer attention to context, and gradually improve the quality of my suggestions.

Leave a Reply

Discover more from Kathleen Venegas – WPCredits Portfolio

Subscribe now to keep reading and get access to the full archive.

Continue reading