About me

I’m Diego Gutiérrez, a Systems Engineering student at Universidad Fidélitas (final term) based in Costa Rica. I approach technology with an analytical, collaborative mindset and a strong self-learning drive. My academic and professional interests focus on building reliable solutions that connect business needs with solid execution, especially across project management, .NET, SQL, Microsoft Power Platform, and enterprise ecosystems such as SAP/ABAP.

This site supports my final project for the course “Computación y Sociedad”, where I’m contributing to the WordPress community while strengthening my understanding of WordPress as a platform and as an open-source ecosystem. If you’re visiting for the first time, feel free to explore my contributions and follow the progress as it develops.

Check the Contributions section to see what I’m working on and the evidence behind each update.

What This Site Is

This website is a single-page portfolio created to document my contributions to the WordPress community, as part of my final project for the course “Computación y Sociedad” in the Systems Engineering program at Universidad Fidélitas. The goal is twofold: (1) to track and present tangible work delivered to the community, and (2) to build practical familiarity with WordPress by using it to publish structured, verifiable progress.

You will find four key areas: About Me (context and background), What This Site Is (purpose and scope), Contributions (a summary of what I have delivered through translation work). Updates will be published whenever new contributions are completed, so visitors can follow the project’s evolution over time.

Visit Contributions and Evidence to review the deliverables and track progress end to end.

Contribution Project Kickoff: Polyglots (es_CR)

Today I kicked off my WordPress contribution project for the Polyglots team, focusing on Spanish (Costa Rica) – es_CR. My scope is the WordPress 4.7.x → Continents & Cities project on translate.wordpress.org. The objective is to translate strings marked as Untranslated while maintaining consistent terminology and respecting localization standards.

Before translating, I defined basic quality rules: proper nouns stay unchanged (city/island names), diacritics must be correct, and terms should remain consistent across the set. I also reviewed the Locale Glossary to avoid introducing variants that conflict with established usage.

This project is part of my final work for the course Computación y Sociedad (Systems Engineering, Universidad Fidélitas), and this website will document progress and evidence as I submit translations.

Workflow & Quality Criteria for Continents & Cities

In this update, I’m documenting the workflow I used to translate efficiently without sacrificing quality. I worked directly in translate.wordpress.org, applying filters to focus on strings needing attention and submitting translations in consistent batches.

My main quality criteria were:

• Proper nouns (cities, islands, regions as names) remain unchanged.
• Geographic terms must be consistent (e.g., Pacific/Indian → Pacífico/Índico).
• Accents and capitalization must follow Spanish norms.
• When uncertain, I validated against the Locale Glossary and kept wording neutral to fit the broader WordPress context.

A key takeaway: even “simple” strings require attention because small inconsistencies can scale across the product. I also noticed that many entries require judgment calls between literal translation and established naming conventions.

Translation Batch 1: First Submissions and Consistency Checks

I completed the first batch of translations for Continents & Cities (es_CR). The focus was to establish a consistent baseline: once a convention is chosen (e.g., keeping city names untouched), it must be applied across all similar entries to avoid mixed patterns.

During this batch, the main decision was distinguishing what is a proper noun versus a translatable geographic term. Cities and islands were treated as proper nouns. For items that are standard Spanish forms, I used correct spelling and accents (for example, África). When I encountered uncertainty, I checked the Locale Glossary and avoided inventing variants.

All submissions are currently in Waiting status, which is expected since approvals depend on translation editors. This reinforces that WordPress contributions are collaborative and governed by shared standards rather than individual preference.

Translation Batch 2: Handling Repetition at Scale

Batch 2 was about volume and repetition: translating at scale means your decisions get amplified. To manage this, I reused consistent patterns and continuously scanned for edge cases that might break the rule set.

The most frequent pattern remained: city names unchanged, with careful attention to diacritics where applicable. I also ensured that translated geographic terms did not drift into multiple variants. When the glossary did not explicitly answer a case, I prioritized the most standard Spanish usage and consistency with previous submissions.

Everything submitted remains in Waiting. This status is important evidence of the workflow: contributors propose translations; editors validate and approve them based on team conventions. It’s a controlled pipeline that protects quality across the platform.

Translation Batch 3: Glossary Questions and Decision Discipline

In Batch 3, the main challenge was glossary ambiguity. Some terms are straightforward, but others depend on local convention and how WordPress expects the string to be used in context. When I wasn’t fully confident, I followed a decision discipline: (1) check Locale Glossary, (2) compare similar strings already translated, (3) keep wording neutral and consistent, and (4) avoid over-localizing proper nouns.

This process helped reduce the risk of inconsistent translations that would later require rework. It also highlighted a key learning: translation contributions are not just language tasks—they are quality management tasks supported by standards, review, and community governance.

Submissions remain in Waiting status, reinforcing the collaborative approval process.

Translation Batch 4: Edge Cases and Final Push

Batch 4 focused on finishing strong and dealing with edge cases. The closer I got to completion, the more important it became to ensure that late translations matched the conventions established earlier. I reviewed patterns across previous batches and corrected any inconsistencies before final submissions.

The recurring standard stayed the same: cities/islands kept as proper nouns, while standard Spanish forms and accents were applied where appropriate. I also kept an eye on formatting and avoided introducing inconsistent punctuation or capitalization.

At this point, the work feels less like “translation” and more like structured contribution: consistency, governance, and traceability. All submitted strings continue to show as Waiting, which is expected until editors review them.

Results Summary: 508 Strings Submitted (Waiting Review)

This update summarizes the results of my Polyglots contribution. I completed and submitted 508 translation suggestions for Spanish (Costa Rica) – es_CR, within WordPress 4.7.x → Continents & Cities. The platform currently shows these suggestions in Waiting status, pending review by translation editors.

What matters most here is traceability: my contributions are visible under my translation profile (diegog120) and within the project’s contributor table. This creates an auditable record of work delivered and supports the purpose of this site: documenting progress and evidence for my final project in Computación y Sociedad (Systems Engineering, Universidad Fidélitas).

Next, I will monitor feedback and approvals, and if changes are requested, I will adjust translations to align with team standards and glossary conventions.

Reflection: What I Learned from Contributing via Polyglots

This final update focuses on reflection. Contributing through Polyglots showed me that WordPress is not only a technology platform—it is a structured community process. My work required more than language knowledge: it required consistency, adherence to shared standards, and respect for collaborative governance.

The main learning was decision-making under ambiguity. When the glossary did not fully resolve a case, I learned to prioritize consistency, avoid unnecessary localization of proper nouns, and submit translations that fit the broader product context. I also gained practical familiarity with how contributions flow from suggestions to editor review and eventual approval.

Wrap-Up: WordPress Polyglots Contribution

Today I’m closing my WordPress Credits contribution project with a short wrap-up. As part of my final project for course Computación y Sociedad (Systems Engineering, Universidad Fidélitas), I contributed to the Polyglots team by working on Spanish (Costa Rica) – es_CR in translate.wordpress.org.

Scope: WordPress 4.7.x → Continents & Cities
Result: 508 translation suggestions submitted

Throughout the project I focused on consistency and localization quality: preserving proper nouns, applying correct accents and capitalization, and keeping terminology aligned. This experience helped me understand how open-source contributions are governed through shared standards and editorial review.

▶ Wrap-up video (WordPress.tv)

If you want to see the full timeline, visit the previous progress posts and the evidence screenshots associated with each batch.