Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Spanish is an active MDN Web Docs locale. To translate a page, work in the mdn/translated-content repository: check the page’s existing Spanish version and open work, prepare the locale file and metadata, translate it according to MDN’s guidance, then submit a pull request for review.
Start with MDN’s Spanish localization guidance
MDN’s localization page lists Spanish among its active locales and directs contributors to the translated-content repository. Read the repository’s contribution guide and translation guidelines before editing; they explain the repository conventions and review workflow.
MDN recommends understanding the English source well enough to translate its meaning and being fluent in the target locale. Small typo fixes are an exception to the English-language prerequisite. Spanish community channels listed by MDN include Matrix’s #mdn-l10n-es, Telegram’s MDN l10n ES, and Discord’s #spanish.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCheck whether the page needs a new translation or an update
Find the English page and its corresponding Spanish page in the repository before you begin. Also check the page’s related issues and pull requests: another contributor may already be working on it, or the Spanish page may need an update rather than a first translation. An April 2026 issue about Web/HTML/Guides, for example, asked interested contributors to comment to avoid duplicate work; that request applies to that issue, not automatically to every page.
#1 Best Overall
Translate a new MDN page into Spanish
- Find the English source. Locate the page in the English content repository, mdn/content, and identify its path.
- Create the matching Spanish file. In
mdn/translated-content, follow the same content structure under the Spanish locale directory,files/es/. MDN’s guide demonstrates the process with a French path; use the equivalent Spanish locale path for Spanish work. - Prepare the front matter. Remove fields that are not needed for the translated page, localize
titleandshort-titlewhen present, and addl10n.sourceCommitwith the latest commit that modified the English source file. - Translate the content. Follow MDN’s translation guidelines and Spanish conventions. Preserve API names, property and method names, variables, and Kumascript macros rather than translating or altering code identifiers.
- Review links and formatting. For links to MDN pages in the same locale, use Spanish paths such as
/es/instead of/en-US/, where appropriate. Check that the translated page retains the source’s technical meaning and structure. - Commit and propose the change. Commit your work, push the branch, and open a pull request against
mdn/translated-content. For a small edit, GitHub’s web interface can guide you through creating a fork and branch; substantial changes can be made with local clones of the upstream and translated-content repositories.
Update an existing Spanish translation
Compare the Spanish page with the current English source and with the page’s history. The repository guide’s detailed instructions for updating translations are unfinished, so there is no complete universal update algorithm; the amount of work depends on how the two pages differ.
- Add sections or details present in the current English source but missing from Spanish.
- Remove material that no longer appears in the source, when it is no longer appropriate for the translation.
- Update
l10n.sourceCommitto the latest commit that modified the English source. - Check Spanish conventions and internal MDN links, including whether links should point to
/es/. - Preserve technical names, code identifiers, and Kumascript macros.
- Review the page’s issues and pull requests and coordinate with other contributors if work is already underway.
An MDN Spanish localization issue opened April 16, 2026 illustrates this kind of checklist, but each page’s changes and status must be checked individually.
Rank #2
- Over 40, 000 entries including English pronunciations given in the International Phonetic Alphabet (IPA).
- A compact guide to essential Spanish and English vocabulary.
- For ages 13 and up.
- Bi-directional: English to Spanish and Spanish to English.
What to expect from the review process
A pull request proposes your changes for review; it does not mean the translation is immediately published. Follow the repository contribution guidance and respond to review feedback in the pull request. MDN’s English documentation comprises close to 14,000 pages, according to its localization page last modified May 31, 2026; that is an approximate English-page count, not a count of Spanish translations or an estimate of Spanish coverage.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
- Designed for student use anywhere
- Hands-on learning resource any time you need to reference a word
- Makes a great gift for new high school or college graduates
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
