One Content Fragment to manage all LanguagesNew
Request for Feature Enhancement (RFE) Summary:
Improve multilingual content management in AEM by enabling a single content fragment to support multiple languages/locales through a tabbed or variant-based interface.
Use-case:
Our content authors manage over 500,000 content fragments across 12 languages. Currently, each language requires a separate content fragment, resulting in significant manual effort and complexity when performing routine tasks such as updates, moves, deletions, and publishing.
Current/Experienced Behavior:
AEM requires a separate content fragment for each language or locale.
Authors must manually replicate actions (e.g., move, update, unpublish, delete) across all language versions.
Shared fields must be updated individually in each of the 12 language-specific fragments.
This leads to a high risk of inconsistency, increased maintenance overhead, and a time-consuming authoring experience.
Improved/Expected Behavior:
Enable a single content fragment to
