How to Translate MDN Web Docs to Spanish

Good day! Translating documentation into different languages is more important than ever. With the growing number of Spanish-speaking web developers, ensuring they have access to updated resources is crucial. In this article, I’ll guide you through the process of translating MDN Web Docs into Spanish, based on a recent initiative that aims to make these resources more accessible.

Understanding MDN Web Docs

MDN Web Docs is a popular platform that documents web technologies like HTML, CSS, and JavaScript. It is an open-source project, which means anyone can contribute to it. As of May 2026, MDN contains nearly 14,000 pages in English, with translations available in several languages, including Spanish. This initiative is part of a broader effort to support developers around the world.

Why Translate MDN Web Docs?

The Spanish version of MDN Web Docs has not been updated as frequently as the English version. By translating this documentation, we can help Spanish-speaking developers access the latest information and improve their skills. This effort not only benefits individuals but also strengthens the global developer community.

Getting Started

Step 1: Familiarize Yourself with the Guidelines

Before you start translating, it’s essential to understand MDN's writing and translation guidelines. These guidelines ensure consistency and quality in the documentation. Key resources include:

• Writing Guidelines: These cover what to document and how to write it.
• Translating MDN Pages: This guide provides a step-by-step process for translating content.

Step 2: Set Up Your Development Environment

To contribute, you need to set up your development environment. Here’s how:

1. Fork the Repository: Create a personal copy of the mdn/translated-content repository on GitHub.

2. Clone the Repository: Download the repository to your local machine using Git. You can do this with the following command:

   git clone https://github.com/YOUR_USERNAME/translated-content.git

3. Install Necessary Tools: Make sure you have a text editor (like Visual Studio Code) and Git installed on your computer.

Step 3: Translate Content

When translating, follow these best practices:

• File Paths: Do not translate file paths. They should remain the same across all languages.
• Front-Matter: Translate the title and short-title fields but leave the slug and l10n.sourceCommit fields unchanged.
• Links: For internal links, change the locale prefix from /en-US/ to /es/. External links should remain unchanged.
• Text Formatting: Keep the original formatting for bold and italic text.
• Images: Do not copy images into the Spanish folder. The build process will pull them from the English folder. Only translate the alt text.
• Callouts: Do not translate callout markers like [!NOTE] or [!WARNING]; only translate the content within them.

Step 4: Engage with the Community

MDN Web Docs has a vibrant community of contributors. Engaging with this community can provide support and enhance your translation efforts. You can find discussions and connect with other contributors through the MDN community portal.

Step 5: Submit Your Contributions

After translating the content, submit your changes via a pull request (PR) on GitHub. Make sure your PR follows MDN's contribution guidelines and passes all checks before merging.

Conclusion

Translating MDN Web Docs into Spanish is a valuable way to contribute to the developer community. By following these steps, you can help make web development resources more accessible to Spanish-speaking developers.

Merits

• Provides updated resources for Spanish-speaking developers.
• Strengthens the global developer community.
• Encourages collaboration and open-source contributions.

Demerits

• Requires time and effort to ensure quality translations.
• May need ongoing updates as the English version changes.

Caution

This article is meant for educational purposes. Remember to replace any placeholder values with actual content when contributing. Always verify claims against the original source before relying on them.

Frequently asked questions

• How can I contribute to MDN Web Docs? — You can contribute by translating existing documents or creating new ones following the guidelines provided.
• What tools do I need to translate MDN Web Docs? — You need a text editor and Git installed on your computer to manage your contributions.
• Are there specific guidelines for translating? — Yes, MDN has detailed writing and translation guidelines to ensure consistency.
• Can I translate images in the documentation? — No, do not copy images; only translate the alt text.
• What should I do with internal links? — Change the locale prefix from /en-US/ to /es/ for internal links.
• How do I submit my translations? — Submit your translations via a pull request on GitHub after ensuring they meet the guidelines.

Tags

#mdn #translation #opensource #webdevelopment #documentation #spanish #programming #community #contribution #guidelines