Using AEM Sites Launches with Translation/Localization ahead of a scheduled website update

[AmberOo1]

Ahead of a major content update, multiple pages on a hotel website need to be updated and also translated and localized to regional sites. From what we've gathered, Translation does not happen within Launches. We believe Launches is still the best approach to help manage the various content edits, but we haven't been able to find documentation that details this entire use case. This is how we understand the process:

1. Create the Launch and add pages (which are copies of source pages)
2. Edit the content within Launches (does not impact source pages)
1. If setup with inheritance, any changes to source pages are auto updated to the launch copy
3. Promote the Launch
4. Run translation 
5. Perform final UAT
6. Publish

Concerns/Questions:

- If Launches is used to manage the content edits, at what point would we promote the Launch and trigger the Translation?

- What is the recommended approach to UAT/getting stakeholder approvals on the content between Launches > Translation and Publish?

- Anything else we need to consider?

Any advice and learnings from similar use cases is greatly appreciated. Thanks!

Ref: 

• AEM Sites Launches Feature
• Translation Best Practice
• Launches in AEM as a Cloud Service
• Launches for Pages
• AEM Sites Translation Journey

[Hemant_arora · Accepted solution]

Promote Launch first, then trigger Translation.

Other considerations:

1. If your regional sites are set up as Live Copies, make sure blueprint rollouts and translation syncs don’t conflict.
2. If assets (images, PDFs) are being updated alongside content, ensure they are included in translation packages 
3. Validate translation

[zen_____]

Our translation workflows may take days to complete since we use human translation. If we have to promote the Launch prior to translation, the pages with sensitive launch content are now at risk of being published during the translation window. Is there any better way to solve this issue?

[kautuk_sahni]

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