associate multilingual Content Fragments in AEM

[Vishal_Kagde]

Hi Community,

I’m creating Content Fragments for multiple languages in AEM. Each translation ends up as a separate fragment with its own UUID.

Is there a recommended way to link or associate these fragments together so we know they represent different translations of the same object?

Thanks for your help!

[SantoshSai · Accepted solution]

Hi @Vishal_Kagde,

Content Fragment is stored as its own asset in the JCR, which means every translation will indeed have a separate UUID. There isn’t an out-of-the-box “translation link” field, but Adobe provides best practices for associating multilingual fragments:

1. Use Language Root Folders

   • Place your CFs under language-specific folders, e.g.

     /content/dam/project/en/fragmentA /content/dam/project/fr/fragmentA /content/dam/project/de/fragmentA

   • This way, AEM’s Multi Site Manager (MSM) and translation workflows know which CF belongs to which language.

2. Leverage AEM Translation Integration

   • If you use AEM’s built-in translation integration (with a TMS), AEM automatically maintains the relationship between the source CF and its translations.

   • The source fragment acts as the master, and translated versions are linked through the translation project.

3. Custom Metadata (if needed)

   • If you are not using AEM translation projects, you can add a custom metadata property (e.g., masterId) in your CF model.

   • Store a shared ID in each translation so they can be programmatically associated later.

References: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/content-f...