This topic describes how you might schedule new content to automatically replace existing content.
For example, if you have a hero that’s published, and you want to change it on a specific date and time, you create two versions:
- A published version with an end date/time that’s earlier than the scheduled start time of the replacement
- A scheduled replacement version with the changes and a start date/time
You can only schedule entire component blocks. You can’t publish individual components by themselves.
Display rules
The following rules determine which content appears:
- Scheduled content has priority over unscheduled content.
- If you have more scheduled content than the publishing limit of either five or 20 rows, the additional content isn’t shown.
- After content expires, it continues to appear in Vega administration until the system automatically deletes it. This can take up to 24 hours. You can manually delete components anytime.
Example
| Setup | Result |
|
The home page has 5 published component rows. |
On 8/5/24 at 5:00 AM, the following changes occur: |
|
|
|
|
Component A stays on the admin draft view until the system automatically removes it (this might occur the next day). You can manually delete component A to free space for another component.
A sample scenario
To determine which content to display, the system first checks the start date and then the start time.
Setup
If the published home page shows:
- Component A: start date/time and end date/time
- Component B: not scheduled (evergreen)
- Component C: start date, no end date
- Component D: start date/time and end date/time
- Component E: start date/time and end date/time
- Component F: scheduled with a start date and end date
Result
On component F’s start date, component F replaces component B.
On component F’s end date, component B reappears provided there isn’t a new component with a scheduled start date. This way, you can create backup content that appears when you don’t have time-bound content.
See also