[Phase 2] - Multi Site and Multi Language use-case (MSM related) #65
Description
Per SC Feedback document
Customer reality (today, AEM Publish):
• Multi-Site Manager (MSM) with blueprints, live copies, fine-grained inheritance (Sites, XFs, CFs).
• Launches, translation projects, global-to-local workflows.
• Used heavily by global brands (FSI, Pharma, Retail, M&E, Travel) to run 50–100+ locales/brands with strict governance.
DA+EDS reality:
• No AEM MSM. DA has its own translation + rollout model (language/locale/hybrid) with configurable rollout behaviors, but it is closer to a disciplined pattern than a full MSM engine.
• Works for “few languages, constrained rollout patterns,” not for deeply nested, multi-brand, multi-locale estates.
Use case to support:
“Global card issuer / airline / streaming brand runs a global site with 1 master + 20+ locales. They expect:
• Single ‘language master’ per domain/brand.
• Consistent rollout of updates with the ability to override locally.
• Clear visibility into what is inherited vs. overridden.
• Safe operations at scale (rollout hundreds of pages without surprises).”
Demo script ask:
- Show a DA-powered site with:
• One language master folder and 3–5 locales.
• A documented, visually clear rollout pattern (e.g., language-only and locale-only variants). - Demonstrate:
• Updating a component in the master and rolling it out with clear options (merge vs override vs skip).
• Local override in one locale that is preserved across future global rollouts.
• Simple ‘where used’/impact view before and after rollout. - For future roadmap: show how this pattern could eventually align to or co-exist with classic AEM MSM for hybrid estates.