Multi Locale handling with Sitemaps and Pages

Agility makes the assumption that if you have multiple locales, your sitemaps, pages and components will essentially be equivalent across each locale.

What that means is that for each page on your sitemap, while it can have a different slug for each locale, it will have the same components on it. When you add or remove a component from a page in one locale, it will add or remove that component in all locales that page exists in.

You don’t have to populate the content for each component on a page if you don’t have content for it. Components that show up a as “New” on a page will not render through the website frontend.

One of the things that can be disconcerting for users who only operate in a specific locale at a time is seeing the version history being update for a page in a locale that they haven’t used. This is 100% OK – it’s just Agility creating a new version of that page to accommodate the addition or removal of a component. That change will not be published to the website until your team actually publishes it.