Translation groups explained

Some CMSs store all languages inside one record. ATLAS gives every language version its own entry and links them in a translation group. It sounds like a small detail, but it shapes the whole editing flow.

Why separate entries

• Each language has its own draft, review, schedule and revision history. The Indonesian page can go live tomorrow while the English one is still in review.
• Each language can have its own path, for example /about and /id/tentang, while ATLAS still knows they are the same page.

What the group gives you

• Correct hreflang. The page payload lists its translations, and the layer writes the hreflang links and the canonical URL for every version.
• A language switcher that lands on the same page in the other language, not on the home page.
• Outdated translation warnings when the source changes after a translation was written.
• Grouped lists in the dashboard: one row per page with every language beside it, plus a filter for pages still missing a language.

Add a translation

Open the entry, choose the language and start the translation. It joins the group automatically. Settings that point at a page, such as the front page and the posts page, point at the group, so they follow every language.