Scheduling content changes while allowing other content to be published

[KevinBo12]

New to AEM and curious on how to handle a basic task for scheduled content.
So ideally we would like to schedule things like banners for offers however if we do this it means any other content published between now and the scheduled time (maybe some seo needs changing) will push all the scheduled changes live as well.
As far as i can tell someone would have to undo the scheduled changes, make their changes and then re-apply the scheduled task. This can't be how other people are managing this so was hoping for a point in the right direction on the correct method.

[giuseppebag · Accepted solution]

hi @KevinBo12 ,with AEM's Launches features, 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:

1. 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.

2. 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.

3. 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.

4. 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.

 

[KevinBo12]

Thank you so much, this is incredibly helpful. I knew there had to be a sensible solution built in.

[KevinBo12]

@giuseppebag 
Hi sorry me again,
On your last point, i can see from the docs i'd need to create a workflow launcher to pick up the promoted pages. Just curious do you know if there's any reason this may be a problem on an EDS site? I asked them what the path should be when i was setting it up and got back far more questions than i was expecting.