Translate a Multilingual Site with AI
Two translation systems can run on the same site, and this skill covers both:
| Part | What it holds | Section |
|---|---|---|
Rosey locale JSON (rosey/locales/{code}.json) |
Shared UI and any page text tagged with data-rosey — nav, footer, headings, buttons, breadcrumbs, and (for non-split pages) whole page bodies |
Part 1 |
Content collection files (blog_fr/, content_fr/ …) |
Per-locale body content + frontmatter (title, description, alt text, page-builder text) that the SSG renders natively per locale | Part 2 |
Most Rosey sites only need Part 1. Only reach for Part 2 if the project actually has per-locale content directories: split-by-directory (the make-site-multilingual skill, Phase 8), or Hugo languages (its Hugo setups A and B). On a Rosey site, a split-by-directory page needs both: its body comes from a content collection file (Part 2), its shared UI from the locale JSON (Part 1). A Hugo site without Rosey (setup A) needs only Part 2.
This skill is written for AI coding agents, but the process works with any AI tool that reads and writes JSON.
When to use
- Locale files have untranslated entries (
valuestill equalsoriginal, and the entry wasn't deliberately kept) - A source string changed and its translations are now stale
- A new locale needs bulk-translating from scratch
- Per-locale content directories (
blog_fr/,blog_de/) need their bodies and frontmatter translated
When not to use
- The site has nothing to translate into yet — no
rosey/locales/, and no per-locale content directories. Set it up withmake-site-multilingualfirst. - Adding a new locale to the build — that is a pipeline and config change, also
make-site-multilingual - Translations come from a human team or an external service — this skill only covers filling the files with AI
Contents
| File | Covers |
|---|---|
| SKILL.md (this file) | Which part applies, and why the file format suits AI translation |
| locale-files.md | Part 1, most sites need only this — rosey/locales/{code}.json |
| content-directories.md | Part 2 — per-locale content directories, only if the site is split-by-directory |
| scripts/README.md | The prepare/merge scripts both parts drive |
Why Rosey files are ideal for AI
Rosey locale files are flat JSON with a predictable three-field structure per entry. That gives an agent three properties that make translation efficient and safe:
- Incremental — new entries from
write-localeshavevalueset to the source original. Comparingvaluetooriginalinstantly identifies what's untranslated; already-translated entries are left untouched. No diffing, no external state, no tracking database. - Deterministic / idempotent — running the same pass twice produces the same output. No re-translation of existing work, reviewable
git diff. - Context-rich — keys encode where text appears (
nav:about,index:hero:title,blog:recent-posts), which disambiguates short strings ("More", "Back", "Home") without a screenshot.
The data format is the state management: read a JSON file, find entries where value === original, translate them, write the file. The one exception is an entry deliberately left the same as its original (a brand name); merge-translation.mjs records those in rosey/translate-site-keep.json so they aren't offered again.
Learnings and Gotchas
This section is a living document. When you discover new patterns, issues, or improvements while translating, ask the user before appending them here. See the repo README's Key conventions → Living documents.