Hi @Luca_Moreau,
To support locale-specific Experience Fragments without duplicating content manually, follow this best-practice approach using Live Copies:
-
Create a master XF:
Author your Experience Fragment at a master location, eg. /content/experience-fragments/site/master/global-banner.
-
Use MSM (Multi Site Manager) to create live copies:
Use AEM’s built-in Live Copy mechanism to create locale-specific versions, e.g.:
/content/experience-fragments/site/en/global-banner
/content/experience-fragments/site/fr/global-banner
/content/experience-fragments/site/es/global-banner
-
Enable rollout configs for XF:
Use rollout configurations such as Push on Modify or create a custom rollout config if needed to manage updates from the master XF to locale-specific ones.
-
Customize locale variations only when needed:
Authors can override only the text or components that need localization while inheriting the rest from the master. This ensures reusability and scalability.
-
And use language root mapping on pages:
Dynamically reference the XF via page language context using a pattern like:
/content/experience-fragments/site/${currentPage.language}/global-banner
This way, you avoid content duplication and keep localization structured and manageable.
Santosh Sai

