It might sound obvious, but content management is about more than just content creation and editing. It is also knowing when your content has reached the end of its useful lifespan. It means knowing when it’s time to ‘Move to Trash’, and when it’s time to ‘Move to Trash’ permanently!
I’ve seen as many content management systems ultimately fail due to poor on-going content control by editorial teams as I have through poor initial implementations by developers. There are many reasons that your content can grow out of control. When it does, your CMS becomes nothing more than a publishing platform and a quite inefficient one.
“I’m sure I’ve written an item like that before…”
“Yeah, it’s in here somewhere, I just can’t find it…”
“I don’t think that content is used but I’m not sure, so I didn’t archive or delete it, just in case…”
Tidying up after yourself whatever your discpline, is just good practise. Whether its content, a codebase or your email inbox. Being scared to delete is a sign that you aren’t in control.
One of the editors I work with on an EPiServer site wasn’t scared to delete content, but he was overawed by the effort needed to discover unneeded content.
This got me thinking. There must be a better and easier way than trawling through a hierarchical tree…
Content reporting using a slice
EPiServer recently reintroduced PowerSlice as a ‘supported’ add-on. PowerSlice uses EPiServer Find to give editors a view of content which goes beyond the traditional hierarchical structure. It allows developers to very easily ‘slice up’ content in any number of ways.
Whilst thinking about the best way to implement a feature for editors to report on unused content, it dawned on me that creating a slice for ‘unused content’ would be incredibly easy
- PowerSlice already has a well-thought out user interface
- PowerSlice allows editors to very quickly jump to managing content using the standard EPiServer interface / good for if you want to find and then delete content
I’ve put together two slices, to help editors find unreferenced blocks and media, using standard methods from the EPiServer IContentRepository interface.
Unused Blocks Slice
Unused Media Slice
These slices and PowerSlice were such a good solution that I’d argue that PowerSlice should be bundled out of the box with a Find install. It could perhaps form the basis of a new and more flexible content reporting function? Reporting is something that is in need of a little love in EPiServer 7/8.