My first contribution to the WordPress Training team has been an exciting learning experience. When I joined the team, I was interested in helping make WordPress learning resources more accessible to Spanish-speaking learners. However, I was new to the contribution process and did not know exactly how to get started. Through the team’s documentation, communication channels, and feedback from other contributors, I have begun to understand how open-source collaboration works in practice.
My First Look at the Handbook
Reading the Training team’s documentation was one of my first steps toward understanding how to contribute. The handbook helped me see that contributing involves more than completing a task. It also requires following established guidelines, communicating with other contributors, organizing the work, and being open to feedback.
One useful aspect was learning that translations need to follow a process so that the content remains accurate, consistent, and easy to understand. I also learned that contributors can ask questions and request guidance when they are unfamiliar with a particular step.
At first, some parts of the process were difficult to understand because I was unfamiliar with the team’s workflow and the way translation tasks are organized. The guidance shared by other Training contributors helped me identify the resources I needed and understand how to move forward.
My First Contribution
My first contribution to the WordPress Training team was translating the first lesson of Open Source Basics and WordPress into Spanish. I used Google Docs to prepare the translation and GitHub to follow the contribution process. I also used Slack to communicate with the team and ask for feedback.
After sharing my translation for review, I received valuable feedback on terminology, clarity, and the natural flow of the Spanish text. I applied the reviewer’s suggested changes to improve the translation and make it more consistent and accessible to Spanish-speaking learners.
This experience helped me understand that contributing to an open-source project involves more than completing a task. It also requires being open to feedback, making revisions, and collaborating with others to improve the quality of educational resources.
The main contribution is tracked in GitHub issue #3713, while issue #3714 contains the reviewer’s comments that helped me improve my work.
The Contribution Process
I used several tools and resources during my first contribution:
- Google Docs: I prepared my Spanish translation in a document that could be shared for review.
- GitHub: I used the project’s issue to connect my contribution with the team’s work and request feedback.
- Slack: I introduced myself, asked questions, and communicated with other Training contributors.
- The Training handbook and team guidance: I used the documentation and advice shared by the team to understand the translation process.
After completing my first draft, I shared the document with the team and requested a review. Another contributor reviewed my translation and provided specific suggestions to improve its natural flow, technical terminology, and clarity.
For example, the reviewer recommended replacing literal expressions with more natural Spanish phrasing, such as changing “una receta confiable para reproducir el error” to “instrucciones fiables para reproducir el error.” The feedback helped me understand that a good technical translation should communicate the original meaning clearly rather than follow the English wording too closely.
This review was an important part of my first contribution because it showed me how feedback can improve the quality of educational content.
Communication and Team Collaboration
My first impressions of the Training team have been positive. The team uses communication channels such as Slack to welcome new contributors, answer questions, share resources, and provide guidance. GitHub helps organize project tasks and discussions, while Google Docs makes it possible to share translation drafts for review.
I also learned that contributing to an open-source project involves collaboration and communication, not just working independently. Asking questions, sharing progress, and being receptive to suggestions are important parts of the process.
As a new contributor, I appreciated receiving constructive feedback instead of simply being told whether the translation was correct or incorrect. The reviewer explained why certain changes would make the text more natural, which helped me learn from the process.
My Main Learnings
This first experience taught me several important lessons.
First, translating technical content requires more than knowing two languages. It also requires understanding the subject, choosing appropriate terminology, and considering the needs of the target audience.
Second, feedback is an essential part of contributing to open-source projects. My first draft was a starting point, and the review helped me identify opportunities to improve the wording and consistency of my translation.
Third, I learned that contributing is a collaborative process. Documentation, communication, and review help ensure that the final content meets the team’s expectations.
Finally, I realized that it is normal to have questions when joining a new community. I do not need to understand every step immediately; I can learn by following the documentation, asking for help, and applying the feedback I receive.
Questions I Still Have
Although I have made progress, there are still aspects of the workflow that I would like to understand better.
I would like to learn more about the team’s expectations for completing and submitting a translation, how a lesson is formally approved, and how progress should be recorded in GitHub. I would also like to understand how reviewers coordinate their feedback and when a contributor should move on to the next lesson.
As I continue contributing, I hope to become more familiar with the team’s processes and work more independently while still following the established guidelines.
Conclusion
My first contribution to the WordPress Training team has shown me that contributing to open source is both a technical and a collaborative learning experience. Translating my first lesson into Spanish and receiving constructive feedback helped me understand the importance of clarity, consistency, and communication.
I am grateful for the guidance I have received so far, and I look forward to improving my translation skills, learning more about the Training team’s workflow, and helping make WordPress educational resources accessible to more Spanish-speaking learners.
