#How to implement "Content Staging" feature?

3 messages · Page 1 of 1 (latest)

subtle fog
#

Hi! We are migrating from a feature-rich SaaS CMS and I'm trying to match a feature called Content Staging. Essentially it creates a new version of a page that content editors can work on long term (for large overhaul changes), while the original page can still be worked on (edited and republished) normally. Content-staged pages are shown in a separate section in the UI, and can be worked on independently of the original version. Then when the long term edits are complete and approved, the editor can publish the "content staged" page, which effectively overwrites whatever version the page is currently in. As a bonus, it also allows for batch releases, where you can select multiple content-staged pages and publish them together.

quasi cloak
#

Payload drafts aren’t quite as robust as you’re describing but I could see this being supported long-term. Basically, we’d allow previous versions to be worked on without forcing them to be restored first. A temporary workaround could be to maintain a duplicate draft page, and work on that.