Shipping multilingual marketing sites without the bottlenecks

Launching in multiple languages often collapses under hand-offs and version control chaos. For a global product team, we built a repeatable pipeline that kept marketing, design, and translators aligned from day one.

Codify content ownership

We established a content model that mapped each page section to an owner and a translation status. Astro’s file-based routing made it easy to keep localized variants paired together, while a simple script flagged missing translations during pull requests.

Keep designers inside the workflow

Design tokens generated from Figma fed directly into CSS custom properties. That ensured every locale stayed on-brand without duplicating UI effort. Review builds went live on preview URLs so stakeholders could see updates in context.

Give translators real tooling

Instead of emailing spreadsheets, translators worked in a collaborative TMS with a live preview powered by Astro’s dev server. When strings changed, notifications went out automatically.

The outcome: all three languages launched on the same day, and the team kept the system as the foundation for future product drops.