hi @Mahesh_Gunaje,
with AEM's Launches feature, you can create a set of content changes in an isolated environment without affecting your live content. A launch creates a copy of your content at a specific point in time, which can then be developed and reviewed in isolation.
The process typically follows these steps:
Create a Launch: You create a launch from your live content. This creates a snapshot or a temporary branch of your content tree. All changes made within this launch are isolated from the live content.
Develop Content: You can now make all your changes, including creating, editing, and deleting pages, within the launch. The live site remains untouched and continues to serve its current content. This isolation prevents conflicts and allows you to work on major updates or new features in a safe, parallel environment.
Request Approval: Once the content is ready, AEM's workflow functionality can be used to request approval. You can create a custom workflow that notifies stakeholders, such as a content manager or legal team, that the content is ready for review. The stakeholders can review the content in the launch environment.
Promote the Launch: After you receive the necessary approvals, you can "promote" the launch. This process copies the content from the launch to the live site. AEM provides options for handling conflicts that may have arisen since the launch was created, ensuring a smooth transition. The content is then ready to be published to the live environment.
Pros:
Parallel Content Development
Enables simultaneous editing of current live content and future updates without interference. You can prepare campaigns or content releases in advance without disrupting the live site experience.
Content Freeze Avoidance
Changes on the live site can continue without pushing unfinished or future content live prematurely, so regular updates and maintenance don’t block new release preparations.
Version Isolation
Launches act as isolated versions, allowing thorough QA and staging without risking live content stability.
Automated Sync of Source Updates
Changes made on source content during the launch development phase get automatically replicated into the launch, minimizing rework and ensuring eventual content consistency.
Scheduled Promotion and Activation
Allows you to set and control when the launch content goes live, perfect for timed campaigns (e.g., seasonal offers, product launches).
Reduce Publishing Risks
Since launch content can be reviewed and tested separately, it reduces the likelihood of errors or incomplete content reaching the live website.
Cons:
Content Drift Complexity
Since changes can be made both on source and launch copies, there is a risk of content drift or conflicts requiring careful management and coordination to merge changes correctly.
Increased Management Overhead
Managing multiple copies of pages/sites increases complexity. Teams need clear processes on when to edit source vs. launch and how to handle conflicts or late-stage changes.
Performance Impact
Large launches involving many pages or sites might increase authoring instance storage and processing requirements, potentially impacting performance.
Limited to Page and Site Content
Launches don’t automatically handle some aspects like assets, workflows, or other entities which need separate management.
Learning Curve
Teams new to AEM may require training to properly use launches and understand promotion and conflict scenarios.
