Translate a page

Add a second language to the site and publish a Spanish version of a page at /es/<path>, with hreflang alternates and a per-language sitemap.

Before you start: a manager account to add the locale (site.settings); an author to translate; AI translation needs an AI provider under Site settings → AI and the ai.use permission.

Steps

1. Site settings → Languages. Add es to the locales (the default stays en). Leave prefix the default locale off unless you want /en/... paths too.
2. Open the page to translate. In the right rail, Translations lists the site's languages with missing next to es. Choose Create translation and a mode: Empty (shared fields and the title only), Copy (everything, to edit in place) or AI (text fields and block copy translated with the brand glossary; the draft is marked so a reviewer knows what the model wrote).
3. The translation opens as a draft with its own revisions. Translate the title, the fields and the layout copy. Fields marked shared (media, dates, references, taxonomy) stay in sync with the source; the layout is copied once and then independent.
4. Run Checks, then Publish (or submit for review).

Check the result

• /es/<path> answers 200 and <html lang="es">; the English page still answers at /<path>.
• Both pages carry <link rel="alternate" hreflang="..."> for each other and x-default.
• /sitemap.xml is now an index pointing at /sitemap-en.xml and /sitemap-es.xml.
• Editing the English source after this marks the Spanish version outdated under Translations and in Translations status; the Spanish page stays live until you update it.
• The main menu shows the Spanish labels you set on its items (menu items carry per-locale labels).

Going further

• Localization: translation groups, translatable and shared fields, routing and search per locale.
• Translations in the API (POST /api/entities/:id/translations).
• Build a page with AI for the AI settings the ai mode needs.

Spillway 0.1.0 · Edit this page on GitHub