Multi-lingual content fragment ID

[VickerL]

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.

[arunpatidar]

Hi @VickerL 

CF does support multi lingual,

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

Are you looking for graphQL Api which returns both copies?

[VickerL]

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

[arunpatidar]

Hi @VickerL 

If you know the path then you can access the CF using open API

https://developer.adobe.com/experience-cloud/experience-manager-apis/api/stable/contentfragments/del... 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/aem-con...

[VickerL]

Hi, @arunpatidar ,

Yes, but will there be any association like ID or similar data that can be used to identify and link up the same item of different languages?

Cheers
Vicker

[arunpatidar]

Hi @VickerL 

I can see only the language copies contains the information about source content. Example below

So you can only get reference of source from target language but not vice versa.

[VickerL]

Thanks, @arunpatidar .

Just to clarify, the reference ID only appears when the language CF is created by a language copy. And it won't appear even when the CF is using the same title under a different language folder.

e.g.

/en-US/certain-item

/zh-HK/certain-item

Because for the above case, the CF console can associate the 2 languages by itself.

[kautuk_sahni]

@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!