The Forestry Commission and associated organisations used a bespoke content management system for their intranet and it was due to drop out of support early in 2019. The search for a new intranet platform was on, and I first heard from the Forestry project team towards the end of 2016 when they were exploring options.
Referendum results, resignations and reshuffles have been causing government intranets to adapt and move quickly to keep staff up to date with changes.
I’d been waiting with anticipation for our latest client intranet launch. It’s the nearest I’ll ever get to fatherhood, but these past weeks I’ve been acting like I’m looking after a newborn.
You know that a project is going to go well when the first paragraph of your client’s brief calls for ‘focusing on key user needs and using open source platforms and technologies to deliver improved value for money.’
A move to a new CMS is an ideal opportunity to tidy the intranet, remove the clutter and possibly present things in a better way. You can choose to use your existing content as a basis for the new CMS, or wipe the slate clean and create new content. This guide covers moving content to a new CMS.