Replies: 8 comments
-
|
SilverStripe is another CMS that has this feature (https://userhelp.silverstripe.org/en/4/creating_pages_and_content/campaigns/) |
Beta Was this translation helpful? Give feedback.
-
|
Agree wholeheartedly with this. Similar to my feature request a few years ago: #2116. |
Beta Was this translation helpful? Give feedback.
-
|
Actually have been thinking about this the past few days. Biggest thing holding me back is the naming. “Release” and “campaign” have both been considered but not a huge fan of either of them. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed, not a fan of those names. Here are a few more ideas:
|
Beta Was this translation helpful? Give feedback.
-
|
I don't have an actual name in mind for this feature, but the way I think about it is that it'd be sort of like a "site draft", in that it could basically enable you to put the whole site (or sites) in sort of a draft mode, where authors could add, remove or change content in multiple sections, preview (and share) the whole site as it will look when all of those content changes are made live, and finally, be able to either discard or publish all those changes at once. "Site Draft" or "Site Version" is kinda problematic, but yeah... that's how I think about the concept, maybe a better name could be derived from that line of thinking. |
Beta Was this translation helpful? Give feedback.
-
|
Batch is pretty good. |
Beta Was this translation helpful? Give feedback.
-
|
Logging another platform that has implemented something like this: |
Beta Was this translation helpful? Give feedback.
-
|
This is likely easier in Craft 4 given all the performance improvements around duplicating content for drafts and versions. We have a site where we've built this feature for them and the slowness when publishing all the specific drafts on the predetermined date is the only pain point currently. |
Beta Was this translation helpful? Give feedback.
-
Description
I came across this feature in another CMS recently and thought it was brilliant and worth considering once workflows are on the table. The idea is that content changes can be staged to a specific release rather than published immediately. This would work really well in the Craft ecosystem where elements are extremely intertwined and highly related. The same concept is also used on Google Tag Manager, as another example.
Here are a few example use-cases:
This becomes even more useful outside of workflows when you consider the static site generation implications - imagine not having to worry about triggering 14 redundant builds while adding a blog post due to a bunch of elements being saved during the editing process.
This is practically begging to be done now that the work adding delta saves/change histories, and element revisions is done!
Beta Was this translation helpful? Give feedback.
All reactions