Content staging
Content staging gives your business team the ability to easily create, preview, and schedule a wide range of content updates for your store directly from the Admin. For example, rather than thinking in terms of a static page, consider a page to be a collection of different elements that can be turned on or off based on a schedule. You can use content staging to create a page that changes automatically throughout the year on a schedule.
The term campaign refers to the record of a scheduled change, or a collection of changes that are managed from the Staging Dashboard. The changes can be viewed on a calendar or timeline. The terms scheduled change and scheduled update are interchangeable and refer to a single change.
When you schedule a content change for a specific time period, the content reverts to the previous version when the scheduled change expires. You can create multiple versions of the same baseline content to be used for future updates. You can also step back through the timeline to view previous versions of the content. To save a draft version, simply assign a date on the timeline that is so far into the future that it never goes into production.
Content staging objects and campaigns
When a new scheduled update is created for any of the following objects, a corresponding campaign is created as a placeholder, and the Scheduled Changes box appears across the top of the page. The placeholder campaign has a start date, but not an end date. You can schedule updates to the content as part of a campaign, and then preview and share the changes by date, time, or store view. After a new campaign is created for one object, you can assign it as a scheduled update for other objects.
Content staging workflow
-
Create the baseline content
The baseline is the content of an asset without a campaign and includes everything below the Scheduled Changes section at the top of the page. The baseline content is always used, unless there is an active campaign with changes scheduled for that place on the timeline.
-
Create the first campaign
Create your first campaign with the start and end dates as needed. To make the campaign open-ended, leave the end date blank. When the first campaign ends, the original baseline content is restored.
note note NOTE Campaign Start Date and End Date must be defined by using the default Admin time zone, which is converted from the local time zone of each website. Consider an example where you have multiple websites in different time zones, but you want to start a campaign based on a US time zone. In this case, you must schedule a separate update for each local time zone, and set Start Date and End Date in converted from each local website time zone to the default Admin time zone. -
Add a second campaign
Create the second campaign, with the start and end dates as needed. The second campaign can be assigned to an entirely different time period. When creating multiple campaigns for the same asset, the campaigns cannot overlap. You can create as many campaigns as needed.
note note NOTE All scheduled updates are applied consecutively, which means that any entity can have only one scheduled update at one time. Any scheduled update is applied to all store views within its time frame. As a result, an entity cannot have a different scheduled update for different store views at the same time. All entity attribute values within all store views, which are not affected by the current scheduled update, are taken from the default values, and not from the previous scheduled update. -
Restore the baseline content
If all campaigns have end dates, the baseline content is restored whenever all active campaigns end.
Content Staging dashboard
The Content Staging dashboard provides visibility into all planned site changes and updates. Any day, range of dates, or time period of a campaign can be previewed, and shared with others.
Content staging demo
To learn about content staging, watch this video:
Troubleshooting resources
For help with troubleshooting content staging issues, see the following Commerce Support Knowledge Base articles: