Branching & Granular Publishing Features
A
Adam Barnwell
Provide the ability to create ephemeral branching of both CMS content and canvas/component changes. Enable editors to work on site changes in isolated scopes to avoid accidentally merging changes and inadvertently deploying something in error. Extend this concept such that multiple staging ephemeral staging environments can co-exist.
Introduce advanced publishing features more akin to pull request reviews, whereby it's clear to see the comparison of one environment to another and accept changes between them. Extend this functionality to the publish workflow so deployers have confidence in what changes they are deploying and, crucially, what they are not.
Take the guesswork out of the most critical parts of the software development lifecycle.
Log In
Autopilot
Merged in a post:
Fine-grained publishing
A
Alexander Fjelldal
I want to be able to select what I publish, and on a fine-grained level. Currently, my understanding is that i need to select what NOT to publish to hold it back from public.
Also: I want to be able to publish changes to components, and to do that without publishing other changes to pages where these components occur.
Since sharing candidates for production with people outside the team is only doable from staging, I want to be able to push changes to staging, but from staging i want to select changes to push to prod without having to set changes to draft to keep them in staging.