Summary
Add internationalization to site/ (the Astro-based agmsg.cc marketing site), following the same language set as the desktop app's i18n work: en/ja/zh-CN/zh-TW/ko/es/fr/de/pt-BR.
Mechanism
Use Astro's built-in i18n routing (astro.config's i18n option: locales, defaultLocale), not a hand-rolled scheme — the site already runs on Astro, this is the native fit.
Language switcher
A modern, common pattern: dropdown in the site header (not per-language subdomain/full nav duplication). No specific reference design mandated — use good judgment for something clean and unobtrusive, consistent with the existing site's visual style (Astro + Tailwind).
Scope
- Site chrome/nav/footer strings: all 9 languages.
- Landing page copy: at least
en (source) + ja to start; other 7 languages can follow the same translation pipeline as the desktop app's i18n (AI-generated, no native-speaker review yet — same caveat as the app, note this in the PR).
References
Summary
Add internationalization to
site/(the Astro-based agmsg.cc marketing site), following the same language set as the desktop app's i18n work: en/ja/zh-CN/zh-TW/ko/es/fr/de/pt-BR.Mechanism
Use Astro's built-in i18n routing (
astro.config'si18noption:locales,defaultLocale), not a hand-rolled scheme — the site already runs on Astro, this is the native fit.Language switcher
A modern, common pattern: dropdown in the site header (not per-language subdomain/full nav duplication). No specific reference design mandated — use good judgment for something clean and unobtrusive, consistent with the existing site's visual style (Astro + Tailwind).
Scope
en(source) +jato start; other 7 languages can follow the same translation pipeline as the desktop app's i18n (AI-generated, no native-speaker review yet — same caveat as the app, note this in the PR).References
.ja.mddocs) — same overall initiative, different mechanism (Astro routing vs static file suffixing) sincesite/anddocs/are different kinds of content.