How to demo translations and multi-site rollouts in Document Authoring (DA)
This demo is designed for pre-sales teams showing how DA can support a global brand with one language master, multiple locales, controlled rollout, and safe local flexibility.
Use this scenario for a global card issuer, airline, or streaming brand that operates one master site and 20+ locales with a need for consistent updates, local overrides, and low-risk rollout at scale.
Demo environment
This demo uses a hybrid, language-first localization model that aligns with DA guidance for global sites with a central language source of truth and selective locale variation.
We use the Locale-based (language > region) Google Translate config from https://docs.da.live/administrators/reference/localization/sample-loc-configs and trim down some of the locales in the list.
Copy the translate.json to your /.da/ folder at the root of your site. That JSON configuration powers the Translate app with translations, rollouts, merges, overwrites, languages and locale options.
The normal flow is to go from
/en/ -> other languages as a translation
/language/ -> /language/locales as a rollout
Recommended story
- Start on /en/budgeting-basics and position it as the single language master for the brand.
- Open /fr/budgeting-basics and /en/gb/budgeting-basics in parallel tabs so the audience can see inherited content versus intentional local variation.
- Point out the shared content and the market-specific copy on /en/gb/budgeting-basics.
- Update the shared content on the master page.
- Explain translation and rollout choices using DA terminology: merge when you want to preserve locale edits, overwrite when the master should fully replace local content, and skip when a market should not receive the change yet.
- Roll out the update to the language locales and show that the inherited markets pick up the change.
- Return to /en/gb/budgeting-basics and show that the market-specific content remains in place after rollout because the owner can choose to merge / overwrite their local copy from upstream or keep their local changes.
- Close by showing the list of affected locale pages before and after rollout as a simple impact discussion: which pages inherit the change and which page intentionally diverges.
- You can show both translation and rollout in the same project or keep them separate to drive home both points separately.
Translations from /en/ to other languages and locales
Rollout individually from /en/ to /en/ca/, /en/gb/ and /en/us
Rollout choices to explain
What to emphasize
- One language master per domain or brand keeps the operating model simple.
- Rollout is controlled rather than all-or-nothing, which reduces risk when updating many pages.
- Local teams can override selected content without losing future global improvements.
- The demo makes inheritance versus intentional divergence visually obvious, which is important for enterprise governance conversations.
Hybrid estate roadmap
For future roadmap conversations, position this pattern as hitting the same notes as the classic AEM MSM rather than identical to it or getting into a feature comparison discussion. Same outcome, different / easier way to do it.
- DA can serve high-velocity sites that need localization and rollout controls.
- In hybrid estates, teams can align around a shared operating model: central language source, selective rollout, local exceptions, and governance visibility.