Multi-lingual content fragment ID | Community
Skip to main content
V
VickerL
Level 2
August 26, 2025

Multi-lingual content fragment ID

  • August 26, 2025
  • 2 replies
  • 1036 views

From my understanding, it is common to create multiple content fragments of an object in order to support multiple languages. However, when doing so, we will result in multiple content fragment UUIDs. In such a case, what is the best way to associate these content fragments so that we know they are just different translations of the same object?

 

I have thought of 2 different approaches.

 

1) Simply using the native "title" field as an ID field, input the same value for the multi-lingual content fragments

- This seems to work, but I am not sure if the field should be used as such. And if this will break certain AEM structure in the long run.

 

2) Adding a custom field called "id" and inputting the same value for the multi-lingual content fragments

 

To be honest, it seems like the AEM content fragment is relatively weak in handling multi-lingual. Other solutions in the market usually bundle all languages in a single object... Or did I miss out some basic principles in AEM?

 

Thank you.

2 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
August 27, 2025

Hi @vickerl 

CF does support multi lingual,

https://experienceleague.adobe.com/en/docs/experience-manager-learn/content-fragments-console/editor/language-copies 

 

Are you looking for graphQL Api which returns both copies?

Arun Patidar
    V
    VickerLAuthor
    Level 2
    August 29, 2025

    Hi, @arunpatidar ,

     

    We aware the content fragment editor could link things up. And yes, we are trying to use AEM as a headless CMS and retrieve the CF via API.

     

    Cheers

     

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      September 2, 2025

      @vickerl just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...