The foundations are now well and truly laid for the delivery of the University’s new content management system. The Polopoly replacement is based on the open source Drupal platform and will provide a much better user experience for web editors. It will also deliver responsive content – fit for phones and tablets.

We have over 300 sites and 70,000 pages to migrate from Polopoly into EdWeb – our new Drupal-based Content Management System. We are planning to do this over 3 main migration phases starting in March 2015. We recently started communication with our web publishing community to allocate them one of these phases.

We’ve recently been considering the need to provide a distinct name for the CMS we’re developing to bring clarity to what we are providing, and future project communication.

Managing your website through a large scale (or enterprise-level) content management system can occasionally feel like a frustrating or restricting experience. I know this because I’ve been a web manager myself, and I field enquiries and comments from time to time in this vein. I had one such email recently, and would like to share it […]

At last month’s Web Publishers Community session, I went through how and why the design and navigation of the University website was changing. The slides from the session are available as ever, but I thought it would be good to write a blog post to cover the main points for those that couldn’t make the […]

We’ve been using the insight and suggestions gathered in last autumn’s website content planning workshops to steer the development of content types for the new Drupal content management system.

Our monthly Web Publishing Community meetings provide a convivial forum for the University’s web managers, editors and developers to discuss current projects and new opportunities.

I’ve been thinking about social media sharing buttons recently. This kind of functionality is on the to-do list for the new Drupal CMS. I’m currently wondering whether they’re worth bothering with at all.

One of the most important aspects in embracing Drupal as the framework behind the new CMS of the University of Edinburgh, is engaging with its enthusiastic and creative community. As part of this strategy, the University sponsored Drupal Camp Scotland 2014 and contributed with two, very interesting presentations.

What do you do with 300 user stories instead of a huge business requirements document? How do you put them into some sort of order? Where do you start?