Add a second language to a Hugo blog with paired content files
At a glance
A blogger uses Claude Code to translate an existing Hugo archive and add the configuration and interface needed to browse both languages. This workflow is listed under Localization, Blogging, Static Sites.
- Agents / tools
- Claude Code, Hugo, Git, nginx
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Give Claude Code access to the Hugo site, theme repository and build environment. Identify the existing language, target language and desired voice; this author wanted English and informal Italian. 2) Have Claude add `[languages.en]` and `[languages.it]` sections in `config.toml`, rename existing posts from `post.md` to `post.en.md`, and create translated `post.it.md` counterparts. 3) Add `i18n/en.yaml` and `i18n/it.yaml` for interface strings and a language switcher in the theme. If matching the author's deployment, configure nginx to redirect according to Accept-Language. 4) Commit the content and theme changes, build the site and deploy to staging. 5) Check the rendered result on a laptop and phone, give Claude specific corrections, and repeat the commit/build/staging review loop before publishing the finished version.
How it went
The author reports translating 69 posts during a two-day blog overhaul. Italian translations were useful but imperfect, with technical jargon often remaining English.