Shipping a multilingual site without a plugin marketplace
Author: Dana Okafor at Zitegen
On most site builders, "multilingual" means installing a third-party plugin, hoping it survives the next core update, and manually keeping two content trees in sync forever. Zitegen treats locales as a first-class part of the Pages panel instead of a bolt-on.
Step 1 — add a locale
From the Pages panel, add a sibling locale to any page — say, a Spanish version of your homepage. It shows up as a linked variant of the same page, not a disconnected duplicate you have to remember to update.
Step 2 — let AI draft the translation
Ask chat to translate the page into the new locale. It works from the existing component tree, so structure, styling, and section order carry over — only the text content changes. You're editing a translation, not rebuilding a page from a blank prompt.
Step 3 — wire up the switcher
The locale switcher itself is a marker your compiler resolves at build time, the same way a repeated-articles block resolves into real markup — meaning it's AI-authorable. Ask chat to "add a language switcher to the header" and it drops the marker in; the published site swaps locales without a page reload.
What this doesn't do
It's not a translation memory system and it won't catch every idiom. Treat the AI draft as a fast first pass a native speaker should still review — the same way you'd review any AI-generated copy before publishing it. What it does solve is the mechanical half of going multilingual: the linked pages, the routing, and the switcher UI that used to be a half-day of plugin configuration.