Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

AEM Experience Fragments support locale-specific variations without duplicating content

Avatar

Level 2

Hi,
I am working on a multilingual AEM Sites implementation and using Experience Fragments (XF) extensively for reuse across pages. I want to create localized variations of an XF but without duplicating the entire fragment manually for each language.

Is there a recommended way to manage locale-specific variations of XFs in a scalable and maintainable manner?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Luca_Moreau,

To support locale-specific Experience Fragments without duplicating content manually, follow this best-practice approach using Live Copies:

  1. Create a master XF:
    Author your Experience Fragment at a master location, eg. /content/experience-fragments/site/master/global-banner.

  2. 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

  3. 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.

  4. 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.

  5. 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

AEM BlogsLinkedIn


View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @Luca_Moreau,

To support locale-specific Experience Fragments without duplicating content manually, follow this best-practice approach using Live Copies:

  1. Create a master XF:
    Author your Experience Fragment at a master location, eg. /content/experience-fragments/site/master/global-banner.

  2. 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

  3. 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.

  4. 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.

  5. 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

AEM BlogsLinkedIn