Why do we have seperate content fragments for each language or locale?

[sanjeevkumart45]

I’m still unclear why AEM requires separate content fragments for each language or locale. This setup creates a significant maintenance burden for authors. Wouldn’t it be more efficient to have a single fragment with language variations organized as tabs?

Currently, we have over 500,000 fragments, and managing them across multiple languages is extremely challenging:

• If an author moves a fragment, they must manually replicate that move across all language versions.
• If a shared field is updated, it has to be manually changed 12 times—once for each language.
• If a fragment needs to be unpublished, the author must do it manually for all 12 language versions.
• If they decide to delete it, they will have to do it 12 times.
• We can do some kind of automation. But I feel AEM should take care of it or find a better way.

This process is not only time-consuming but also error-prone. I strongly believe AEM should invest in a more scalable and author-friendly solution to streamline multilingual content management.

[giuseppebaglio]

This is expected and not tweakable at the moment. For instance, all the features available under the context of Multi Site Manager for Sites would be very useful when managing both CF and XF.

It may be helpful to create a post in the Ideas section where you describe your proposal, current situation with your fragments and the desired behavior.

[sanjeevkumart45]

Thank you for your feedback and sending me the link to the ideas section. I will describe my proposal.