{"canonical_url":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/","content_markdown":"# Built a multilingual Hugo site in 3 languages\n\nBuilt a multilingual static site in Hugo across 108 template files including 53 partials, publishing every page in four representations from one content tree in three languages, and again under seven focused subdomains built from that same tree.\n\nAugust 2026\n\n**Situation.** The company needed a public site that works in three languages, proves capability rather than asserting it, costs nothing to run, and does not hand its visitors to anybody. Most of those are ordinary requirements. Together they rule out almost every content management system, because a runtime backend is a thing to secure, to patch, to pay for, and to explain on a privacy page.\n\n**Task.** The site had to be generated entirely at build time and still behave like a modern one — searchable, installable, syndicated, printable, and readable by a screen reader in every language it ships.\n\n**Action.** At the recorded design stage, it was a static site: 108 template files, of which 53 were partials and 18 were shortcodes, three languages, no runtime backend, and one first‑party script granted as a scoped exception for a portfolio filter whose every control was hidden until it ran. Capability was added at build time rather than in the browser, which was a product decision and was written down as one. Every page was published in four representations from one content tree — HTML, a Markdown twin, a Gemini document and a Gopher menu entry — with the home page adding three syndication feeds and an installable‑application manifest on top. The taxonomies were deliberately two rather than one, and the distinction was load‑bearing: a category was a topic tag on the work, a service was something the company sold, and collapsing them would have made the catalogue a list of skills instead of a list of offerings. The same tree was then built seven more times, once per focused subdomain, by pointing the generator at a different content directory rather than by forking anything.\n\n**Result.** At that stage, the site served three languages and four representations from one tree, needed no request‑time application backend or separately billed application service, and its one piece of JavaScript was held to a contract a linter enforced. Beyond that exception, interactive features had to be solved at build time or omitted, which had ruled out several things that would have been easy with an application server and was the reason the search index was costed and parked rather than shipped. This describes the recorded design stage, not the current site's inventory or implementation.\n\n---\n\n- Role: Frontend Engineer\n- Categories: [Frontend Engineering](https://engineer.company/categories/frontend/), [Full‑Stack Development](https://engineer.company/categories/full-stack/), [Web Development](https://engineer.company/categories/web-development/), [Performance Tuning](https://engineer.company/categories/performance/), [Design Systems \u0026 UI](https://engineer.company/categories/design-systems/), [Internationalization](https://engineer.company/categories/i18n/)\n- Services: [Frontend Development](https://engineer.company/services/frontend-development/), [Full‑Stack Product Development](https://engineer.company/services/full-stack-development/), [Website Development \u0026 CMS](https://engineer.company/services/web-development/), [AI Agent Readiness](https://engineer.company/services/ai-agent-readiness/), [Internationalization \u0026 Localization](https://engineer.company/services/i18n-localization/)\n\n\u003chttps://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"At that stage, the site served three languages and four representations from one tree, needed no request-time application backend or separately billed…","formats":{"gemtext":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/index.gmi","gopher":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/gophermap","html":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/","json":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/index.json","markdown":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/index.md","pdf":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/index.pdf"},"kind":"page","language":"en","title":"Built a multilingual Hugo site in 3 languages","url":"https://engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/","version":1}