Puffbox

Late last year, Puffbox helped Defra move its main corporate website over to WordPress. One of the grand concepts underpinning the project was the use of WordPress’s multisite (formerly MU) functionality, allowing us to run multiple websites using the same installation. We launched with only one child site, for News – probably the easiest one, at that. But straight away, we began making much more ambitious plans.

Like everywhere around Whitehall, the start of a new tax year was to bring various contractual and organisational changes at Defra: and it was set as our deadline for the next phase of work, spinning off many more child sites. The good news is, all went well, and they’re now managing 20 distinct sites through the same WordPress installation – some carrying their own identities, some nested deep (and hopefully seamlessly) within the Defra design.

The first task was to rebuild the output themes from scratch – yes, already. For the initial launch, we had simply dropped WordPress code into Defra’s existing Dreamweaver-based output templates, and grafted some additional CSS on to their existing stylesheets, which were already in need of a good clear-out. They were never going to be able to support a platform consisting of literally dozens of child sites.

We now render the pages using something akin to a multi-level theme framework:

• Every site is built on the ‘base’ theme, which defines the layout, and the bulk of the functionality, but has no imagery or colours attached to it. This theme is effectively hidden on the platform, and will never be used directly.
• There’s then a corporate (‘root’) theme, a child theme of ‘base’ in WP terms, which adds the departmental colour scheme and logo. This theme is used by the top-level site, which contains most of the corporate information. It adds a custom template for the top-level homepage, but that’s about it.
• We then have a number of further Defra-branded child themes, defined as children of the ‘base’ theme, but also referencing the ‘root’ stylesheet for colour and branding. Depending on functionality, there may be additional templates or functions: so for example, the News theme/site has its own homepage, and the theme used by the Publications and Statistics sites has its own approach to presenting attached files.
• Finally, there’s a ‘custom’ theme for use by sites within the extended Defra family. This uses the same ‘base’ theme for layout; but includes additional WordPress functionality – mostly built-in, if you know where to look – to customise the branding and colour palette via the admin interface. Upload a logo, choose two colours, and bingo – a unique child site, which still retains the basic house style, maintains its connections to the wider Defra network, but whose management can be devolved to an arms-length business unit. Everyone’s a winner.

Needless to say, there are countless custom functions behind the scenes to stitch it all together – simple things like forcing a particular sitewide tab to be highlighted, to make a child site seem like it’s within a particular branch of the corporate site. (Although actually, that one wasn’t simple at all.)

And there are one or two new custom plugins which add pretty significant functionality, including one to implement a site-wide shared taxonomy. This has the potential to automatically surface related items across the network, and is pretty exciting – although we won’t see its benefits for some time.

As you can imagine, moving such a large quantity of material into such a radically different publishing model has frequently been challenging. We’re still finding our feet in certain areas, and it goes without saying, we’re pushing WordPress harder than ever. A few glitches here and there are inevitable; but we’ve had nothing too catastrophic. With a proper staging environment now in place, all our code being managed through Subversion, and a WordPress-based bug tracker to log any issues, it’s all gone relatively smoothly.

I can’t say enough about the contributions from Simon Wheatley and Team Defra; my front-end work was completed pretty early on, and I’ve really just been a spectator whilst the serious lifting and shifting has been happening. But once again, the Defra guys have been an absolute pleasure to work with, giving us more room to experiment and innovate than we’d ever dare ask for. Thanks guys.

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.