Episerver has a feature called Episerver Projects that allows editors to work and collaborate on a number of changes that are grouped together into projects. This is allows multiple changes to be made to a site that can be previewed and all published at once which is useful for things like campaign launches and site updates. This is a great feature but more than once in the Episerver Forums I have heard of the requirement to revert all changes made in a project.
Thinking about this, an approach could be to create another project to revert the changes made by a project. This allows editors to quickly get back to the state before the project was published. The code to achieve this can be found over at the following Gist: https://gist.github.com/davidknipe/d64f9d9993443fd5443c6a6a9f6dae13 and does the following things:
As of EPiServer Update 87 which released EPiServer.CMS.Core 9.3 and EPiServer.CMS.UI 9.3 the projects feature is now out of beta there is no need to add users to the EPiBetaUsers group
This a quick "note to self" on how to enable the new projects feature in the later versions EPiServer (8+ and 9 at the time of writing) as I constantly forget how to do it.
Once enabled editors get access to the projects feature that includes the project bar at the bottom of the UI as shown below:
EPiServer Projects is one of the key new features in the EPiServer Spring 2015 release. It gives editors the ability to add content items to a project then preview any changes as if they were published. Projects not only allow editors to preview content before its published but can also serve as a useful navigation device to group a set of changes together for editors to work on.
For example editors may need to work on projects such as when a set of articles need to be reviewed or a monthly commerce catalog update. So as developers we may want to programmatically create projects to help editors rather than letting editors manually create them.
This post explores how to use the EPiServer Projects API.