fix(website): es translation gaps — navbar, footer, blog plugin and hero pillar#182
Merged
Merged
Conversation
When the es locale was activated (PR #163) only code.json was translated. The navbar items (Docs, Blog, GitHub), footer columns and links (Adoption Guide, CLI Reference, Workflows, Organization, ...), copyright, and blog plugin SEO/sidebar fell through to English fallbacks. zh-CN already shipped these (PR #177); this brings es to parity. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
montfort
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentación,Blog,GitHub), footer column titles (Documentación,Proyecto,Strange Days Tech), footer link labels (Guía de adopción,Referencia del CLI,Flujos de trabajo,Organización, ...), copyright line, and blog plugin SEO fields.ReleasesandIssueskept in English on purpose — they're GitHub-specific terms and the links point to GitHub itself, which is in English.Why
When the
eslocale was activated (PR #163) onlycode.jsonwas translated. The navbar, footer and blog plugin strings silently fell through to their English fallback values — visible at https://straymark.dev/es/ where the menu reads "Docs / Blog / GitHub" instead of "Documentación / Blog / GitHub".zh-CNshipped these three files when its locale was activated (PR #177); this PR bringsesto parity.These three skeleton files were generated as a side-effect of running
npm run write-translations -- --locale esin PR #181; rather than committing them with English defaults there, they're filled in here in their own PR.Test plan
npm run buildsucceeds (verified locally — all 3 locales build clean)./es/: navbar showsDocumentación,Blog,GitHub; footer showsDocumentación,Proyecto,Strange Days Techas column titles andGuía de adopción,Referencia del CLI,Flujos de trabajo,Organizaciónas link labels; copyright ends withHecho con Docusaurus../es/blog: page title isBlog, SEO description isLa bitácora de StrayMark — cómo emergió el framework, decisión a decisión., sidebar header isTodas las publicaciones./en/and/zh-CN/unchanged.🤖 Generated with Claude Code