Multilingual content — linked translations
When you need the same site in more than one language, a CMS links translations to the same entry — not duplicate websites.
Duplicating your entire site per language doubles maintenance. A multilingual CMS stores English and Spanish (or any locale) as linked translations of the same blog post or page. Update the source language; translators update their version — the link stays intact.
The English version is already published as the original. Use the table below to add linked translations — then switch languages in the preview dropdown.
Translations manager (simulation)
English is done and live as the original language. Click Add on Spanish, French, or Portuguese to create linked translations — the same workflow as the Drupal translations screen.
| Language | Translation | Status | Operations |
|---|---|---|---|
English (Original language) | Published | ||
Spanish | n/a | Not translated | |
French | n/a | Not translated | |
Portuguese | n/a | Not translated |
Front-end preview
The English version is already published. This is what visitors see today — add translations above to offer more languages in the header switcher.Harvest & Steam
Five ways to welcome remote workers
Create a warm, flexible space with reliable WiFi, quiet zones, and all-day coffee — remote workers will keep coming back.
In the CMS admin, editors translate field by field. The translation link keeps every locale tied to the same entry — not a separate copy of the site.This simulation is simplified for learning purposes. With the CMS, these tools are much more powerful and configurable.
Plan languages early
Even a single-language launch benefits from a CMS that supports translation later.
Translate content, not layout
Canvas layout is shared; only text fields need translation per locale.
Workflows can include translators
Assign locale-specific roles so native speakers review before publish.
Tip
You do not need separate sites per country — linked translations scale better for marketing teams.
