Built a multilingual Hugo site in 3 languages
Built 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.
August 2026

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.

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.

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.

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.

Categories:
1Frontend Engineering	/categories/frontend/	software.engineer.company	70
1Full‑Stack Development	/categories/full-stack/	software.engineer.company	70
1Web Development	/categories/web-development/	software.engineer.company	70
1Performance Tuning	/categories/performance/	software.engineer.company	70
1Design Systems & UI	/categories/design-systems/	software.engineer.company	70
1Internationalization	/categories/i18n/	software.engineer.company	70

Services:
1Frontend Development	/services/frontend-development/	software.engineer.company	70
1Full‑Stack Product Development	/services/full-stack-development/	software.engineer.company	70
1Website Development & CMS	/services/web-development/	software.engineer.company	70
1AI Agent Readiness	/services/ai-agent-readiness/	software.engineer.company	70
1Internationalization & Localization	/services/i18n-localization/	software.engineer.company	70

hThis page on the web	URL:https://software.engineer.company/portfolio/built-a-multilingual-hugo-site-in-3-languages/	software.engineer.company	70
