Full English/Spanish localisation, and a CMS-less content layer

Released

Iris Vermeer

The marketing site is now fully bilingual — every page rendered in English and Spanish, with proper hreflang annotations so search engines understand the relationship between the two. No regional shortcomings: button labels, microcopy, FAQ entries, comparison tables, even the legal copy in the footer.

The bigger architectural change underneath: we removed the external content management dependency entirely. Content lives next to the code in a typed content layer, so:

Translations ship through the same review process as everything else, with the same git history and the same checks.
The marketing site has one fewer external service to keep alive (and pay for).
Local development just works — no need to spin up a CMS to render the site.

This is a developer-experience win that ends up being a user-experience win, because content updates now ship faster.

February 21, 2026

Activity feed

Isabella Fernandez
How do non-engineer copywriters interact with the content layer now? Writing copy in YAML or JS files is fine for engineers but it would slow down a content team that does not git.
May 13, 2026
•
Replay
James Whitfield
Fully bilingual EN/ES on the marketing site, including the legal copy in the footer — that is the level of completion I expected took months of work. Quietly impressive.
May 5, 2026
•
Replay
Daniel Walker
A typed content layer next to the code is the right architecture for a small team. One fewer external service to keep alive, version control captures the translation history, and PRs become the review workflow. Solid trade-offs.
March 10, 2026
•
Replay
Yank Carlos
Removing the CMS dependency was a tougher decision than it looks — we lost some flexibility for content-only edits. But the simplicity of having everything in one repo with one review process won. Will revisit if our content velocity outgrows the model.
March 4, 2026
•
Replay