associate multilingual Content Fragments in AEM

Question

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 Answer

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:Use Language Root FoldersPlace 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.Leverage AEM Translation IntegrationIf 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.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-fragments/content-fragments-managing

Sign up

Login with SSO

Login to the community

Login with SSO