A subject which keeps coming up in conversation just now is the planned merger of ‘normal’ WordPress with WordPress MU, the ‘multi user’ version. There’s been both excitement and concern at what it might mean: but the latest report from Jane at WP HQ should be enough to calm anyone’s worst fears.
It was announced at WordCamp San Francisco last year that WordPress and WordPress MU would be merging codebases. This has now happened in 3.0-alpha, and we’re working on smashing bugs and tidying up a few screens. If you’re currently using a single install of WordPress, when you upgrade to 3.0 you won’t see any of the extra screens associated with running a network of sites. If you’re currently running MU, when you upgrade you’ll notice a few labels changing, but upgrading should be as painless as usual. If you’re going to set up a new WordPress installation, you’ll be asked as part of the setup if you want one site or multiple sites, so that’s pretty simple. If you want to turn your single install into one that supports multiple sites, we’ll have a tool for you to use to do that, too. So if you’ve been worried about the merge, have a cup of chamomile tea and relax; it will all be fine. 🙂
It’s quite a relief to see how they’re planning to manage this: most existing users of ‘normal’ WP won’t even see the new functionality, but if they want to make use of it, there’ll be a way to do so. Any impact will be seen by the existing MU user base, but as it’s a more complex product by definition, they should be better able to cope with any changes. That seems like the perfect solution all round.
The feature I’m personally most excited about? Never more having to refer to ‘ordinary’ WordPress, ‘standard’ WordPress, ‘WordPress solo’, ‘non-MU’…
Over the last couple of months I’ve been working with Steph Gray and his BIS colleagues to build a modest little family of websites which could have far-reaching consequences.
As Steph notes on his own blog, I’ve long been musing openly about seeing corporate websites as clusters of smaller websites: making a virtue of the silo mentality, if you like. Give each sub-unit a full-featured website, with hands-on control of content, their own ‘latest news’ stream, the ability to activate and manage reader comments. Let the technology platform enforce a certain degree of consistency, and centralised control. Lay a unifying ‘front end’ over the top, to promote the day’s most important developments, and assist with search and navigation.
It also tied in neatly to a question I’ve been asked quite a few times lately: what’s the maximum number of pages a WordPress build can handle? In a single ‘page tree’, I’ve helped run sites with hundreds of pages – and whilst it’s perfectly serviceable, it’s hardly ideal. But maybe it’s the single page tree that’s the problem there. How about if, instead of a 100-page structure, you had 10 structures each of 10 pages?
The opportunity to test the theory arose when Steph approached me about BIS’s Science and Society site – which, as it happens, had been Steph’s first WordPress build (whilst still in DIUS). What better audience for such an experiment than the science community?
We replaced ‘ordinary’ WordPress with WordPress MU (‘multi user’), and I built a more flexible MU-friendly theme, maintaining the same basic look and feel. There’s a top-level ‘family’ navigation, representing the various individual subsites; and with a line or two of CSS, we can give subsite its own colour scheme. There’s a special ‘homepage’ template for subsite use, driven primarily by widgets. And at the top level, we’re actually aggregating the subsites’ RSS feeds to produce a ‘latest across the whole site’ listing and RSS feed.
It’s a tricky time to be doing the project, on numerous fronts. BIS are working on launching a redesigned (non-WP) site, hence the new blue branding along the top. WordPress v3.0 is on the horizon, integrating MU’s multi-user aspect into the core product, with as yet unknown consequences. Oh, and in case you’d missed it, there’s an election on the cards, not to mention a purdah period leading up to it – and who-knows-what afterwards. So things have been a bit quick-and-dirtier than I’d usually allow; but I saw no point getting bogged down in detail when everything could be up for grabs imminently.
Steph has used a deliberately provocative title on his post – ‘One day, all of this will be blogs.’ Is that an overstatement? Perhaps, but aren’t we seeing blogging steadily take over other forms of communication?
If teams really do want to connect with their stakeholders (hate that word), and operate transparently, and permit two-way conversations – this model would give them the platform they need. A single WordPress MU build makes the maintenance of the network (almost) as straightforward as a single blog – and allows a degree of control to be kept at the centre. The stakeholders can have all the RSS feeds and email alerts they could desire. It doesn’t resolve the human and organisational / cultural aspects: but it clears the way for those to be tackled, if we really want to.
I think it can work: it’s the logical ‘next step’ for WordPress’s journey into the corporate world, surely. Do I think it will work? I honestly don’t know. I’ll be watching with interest.
A few months back, I helped the Department For International Development set up an online consultation site for their white paper on Eliminating World Poverty. We used WordPress (obviously), plus Steph Gray’s Commentariat theme (with a few tweaks). The site was well received, and had close to 500 reader comments, many of them lengthy. So when a new consultation came along, into DFID’s plans to spend £8.5bn on education in developing countries, I’m delighted to say they were keen to do it again.
This time, we’ve done it slightly differently – creating a reusable platform for online consultations, instead of just another one-off site build. Rather than use the Commentariat theme itself, I’ve built a generic DFID-styled theme to fit almost seamlessly into their corporate look and feel; but the defining elements – reverse-dated posts in categories, the floating comment box – are still there.
And significantly, we’ve moved from ‘normal’ WordPress to a WordPress MU (‘multi user’) installation. This brings several important benefits for DFID:
- the ability to create new sub-sites in a matter of seconds, through the WP interface;
- centralised management of platform / plugins / themes;
- one sign-on for all blogs on the system: OK, it’s not ‘single sign-on’ via LDAP or anything, but it’s a start!
- varying levels of user permission: you can give someone ‘admin’ status on a sub-site, and still keep the most dangerous options at the higher ‘site admin’ level;
- once it’s in, you can avoid all the usual IT Department headaches – DNS being a particular problem, I’ve found;
- and yes, it’s also cheaper for them in the long run. They no longer need to hire me to set these things up for them. (D’oh!)
Now having said all that, working with MU isn’t without its issues. Historically it didn’t get quite the same love and attention that ‘normal’ WordPress got; although to be absolutely fair, the delay between ‘normal’ releases and the matching MU releases has been cut right down. Some of its processes and language could be clearer: for example, when is an admin not an admin? When he/she’s a site admin, of course. And how do you make someone a site admin? You type their username into a text box under Options, naturally. (That took me a l-o-n-g time to figure out.)
Coincidentally, as I’m writing this, I get a tweet from COI’s Seb Crump: ‘@simond what’s the tipping point for considering WPMU? Plans for maybe up to 3 blogs eventually, but their launches spread over next 2+years‘
For me, it’s not particularly about the number of blogs being managed: it’s about the convenience of using the single installation. If those benefits I bullet-listed above are of interest to you, then MU is worth doing even if you’re only planning on having two blogs. Particularly in a corporate context, it means you can delegate quite a lot of responsibility to individual staff or departments, whilst still being able to wade in as and when. (And with automated upgrading now built-in, I’d say that’s a bigger issue now than it was previously.) But be warned, MU does have a learning curve. Even as a (normal) WordPress veteran of several years experience, it still beats me sometimes.
But in a 2+ year timespan, it ultimately won’t matter. It was announced in late May 2009 that ‘the thin layer of code that allows WordPress MU to host multiple WordPress blogs will be merged into WordPress’; I don’t believe there’s a confirmed timetable for it, though. That should mean that the MU elements get raised to the same level of perfection as in the ‘normal’ product: unquestionably a good thing, I’d say.
Anyway, back to the DFID project. I’m delighted with the first site to be built on the platform: and the DFID guys have done a great job dressing it up with imagery – it makes a huge difference. But the really exciting part, for me, will be seeing the next one get built. And the next one. And the next one.