Simon Dickson has been blogging about online government, politics and WordPress since 2005. Some important people read it.

 
 

Archive for October 2010


Monday 4 October 2010

Defra relaunches corporate website on WordPress

This morning saw the launch of a new website for Defra, the Department for Environment, Food and Rural Affairs. It looks remarkably like their old one, which was placed in suspended animation after the election. Almost identical, in fact. But behind the scenes, it's a completely different story.

Thus far, Defra's website has largely been managed manually, one page at a time, using Dreamweaver. They started using WordPress two years ago: first a blog, then a Commentariat-based commentable document. Puffbox got involved about 12 months ago, helping develop a couple of microsites. And internally, they've been running a few pilots, notably with their press office. It's all been building up to this morning's unveiling of a new corporate website structure built on a WordPress 3.0-based multisite install.

The 'top level' consists entirely of pages (rather than posts) - a fairly modest number to start with, but all thoroughly reviewed and re-edited. Beneath this will be a collection of subsites, of which only one is in place so far, but it's probably the most significant one - News. There's a parent theme plus one child theme; most of the presentational elements are defined either in the parent theme, or the 'top level' site's settings. But of course, the subsites also feed content up to the top in some places, such as the News area of the top-level homepage.

It feels like we've pushed WordPress to its limits on this one, or certainly closer to its limits than we've ever gone before. Files and images are uploaded and managed through WP's interface, allowing us (for example) to generate and summon thumbnails of multiple sizes for the homepage, whilst storing the highest-resolution images for unspecified future use. ;) We're making heavy use of WP3.0's new 'custom menus'. We do intend to use comment functionality, although not for 'conventional' commenting. And of course, the whole concept is based on WP3.0's multisite function: I wouldn't have been comfortable building this on pre-3.0 MU.

Meanwhile, behind the scenes, we have multiple load-balanced servers, and all sorts of WordPress caching magic - which, although it doesn't sound exciting or glamorous, is what really lifts this project into the realms of serious web serving. Hopefully by now, you won't be in any doubt that WordPress can do plenty - but the question often arises, can it do it at scale? Yes it can - but it's much, much more involved than simply installing a plugin or two. (And sadly, I've seen too many instances lately where developers without much WP experience haven't appreciated that.)

There's so many other little things I could mention: a quick custom plugin to do X, a little widget to display Y, a dash of jQuery to do Z. And then there's the other things we've built, but haven't used or activated quite yet. In fact, to be honest, it's a little frustrating that so much 'cutting edge' stuff is concealed behind a year-old front-end.

Mere words are not enough to express my gratitude to Simon Wheatley, whose genius was only exceeded by his dedication on this one. The Defra gang have been fantastic too: they've done great work over a long period to reach this point. And they gave us more freedom than we would be entitled to expect, to do it 'our way'. Thanks, everyone.

Comments: 6

Sunday 3 October 2010

Civil service managers’ salary details delayed

The coalition's Programme for Government stated that, as part of the government-wide transparency and open data initiatives: 'We will require public bodies to publish online the job titles of every member of staff and the salaries and expenses of senior officials paid more than the lowest salary permissible in Pay Band 1 of the Senior Civil Service pay scale' - namely £58,200.

In a letter to all government departments on 31 May, David Cameron stated that these should be 'published from September 2010'. Well, we're now into October, and said data hasn't emerged.

I'm not entirely surprised to hear from well-placed sources that whilst the mechanics of releasing such data are fairly straightforward, the practicalities haven't been. It would be very, very easy indeed to pinpoint exactly how much even relatively modestly-ranked individuals earn - so it's no surprise that it has caused some, ahem, ripples. (It's still happening though, as I understand it.)

Comments: 3

Saturday 2 October 2010

Why we needed the Open Gov Licence

My post on the new Open Government Licence prompted a quite reasonable question from Carl Morris: 'I'm looking for a reason why they're launching a new licence rather than just using straightforward Creative Commons?' Perfectly reasonable question.

So I was delighted to see a response from Beth Brook at the National Archives - late on a Friday evening, I note, explaining precisely why. It's such a good answer, it deserves a post in its own right.

As you’ll see the OGL is a very similar to Creative Commons and Open Data Commons, as we felt they really good models examples to work from. We did look extensively at adopting Creative Commons licences and worked with Creative Commons through the process. However, we developed our own licence for a number of reasons, and I’ll try to cover the main ones below:

- We needed the licence to cover both copyright and database rights – Creative Commons covers copyright only and Open Data Commons covers database right. Having two licences apply side by side to a large proportion of the information being published by the public sector would be overly complex for the user and for the public sector doing the licensing. The OGL is one licence which covers a wide range of information and content types protected by copyright and/or database right, including source code.

- We needed a licence that can cover all jurisdictions in the UK, including Scotland, Wales, England and Northern Ireland – the Creative Commons UK licence is still forthcoming.

- We wanted the licence to be a simple as possible under one set of terms and conditions rather than having a simple summary on the surface and lengthier, more complex conditions underneath this. The OGL presents summary examples (in the ‘You are free to:’ section), as well as the more legal necessities in just one licence document.

- We have ensured that the OGL is compatible with Creative Commons and Open Data Commons attribution licences.

Further proof, not that we need it, that the National Archives team really are on the side of the angels on this one. I'm so delighted that sheer simplicity was a good enough justification.

Add a comment