Enhance Releases to better support incremental updates on the same page, allowing multiple scheduled changes to coexist without overwriting each other. An alternative way to achieve some of these use cases could be per-slice visibility toggles, which would let users hide/unhide sections without deleting them.

Why?

Currently, Releases in Prismic are great for scheduling updates, but they operate at the full-page level, meaning:

• Only one Release per page can be scheduled at a time. If a user schedules one update and later wants to add another change before publishing, the second Release overwrites the first instead of layering updates/the two pages are synced across releases.

• There’s no way to “queue” multiple changes to the same page. Users need to either wait for the first Release to go live or manually reapply changes when scheduling new ones.

• No quick way to hide/unhide slices. If a section is only temporarily inactive, users must either delete it or create a workaround, like storing it in a draft page.

Proposed Enhancements to Releases

1. Multiple Scheduled Releases for the Same Page (Layered Updates)

   • Allow different Releases to apply updates to the same page independently, without overwriting previous scheduled changes.

   • Example: A marketing team schedules:

     • A holiday sale banner to go live on December 1st.

     • A new “Featured Blog” section to be published two weeks later.

   • Currently, the second update would either overwrite the first or publish both at once. With layered Releases, both could be scheduled separately.

2. Per-Slice Release Scheduling

   • Instead of managing content at the full-page level, allow users to schedule individual slices within Releases.

   • Example: A client wants to add a “Limited-Time Offer” slice for a weekend sale but keep other changes separate.

Alternative Approach: Per-Slice Visibility Toggles

If layered Releases are complex to implement, a simpler alternative could be adding a visibility toggle for individual slices. This would allow users to hide/show slices without deleting them, covering use cases like:

• Seasonal banners: Preloaded in the page and switched on/off as needed.

• Testing different layouts: Designers can toggle slices instead of moving them between draft pages.

Conclusion

Expanding Releases to support multiple scheduled updates on the same page would greatly improve flexibility for content teams. Per-slice scheduling would streamline content workflows, while visibility toggles could serve as a lightweight alternative for temporary changes.