Skip to content

Puffbox

Simon Dickson's gov-tech blog, active 2005-14. Because permalinks.

2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005

Code For The People company e-government news politics technology Uncategorised

api award barackobama barcampukgovweb bbc bis blogging blogs bonanza borisjohnson branding broaderbenefits buddypress budget cabinetoffice careandsupport chrischant civilservice coi commentariat commons conservatives consultation coveritlive crimemapping dailymail datasharing datastandards davidcameron defra democracy dfid directgov dius downingstreet drupal engagement facebook flickr foi foreignoffice francismaude freedata gds google gordonbrown governanceofbritain govuk guardian guidofawkes health hosting innovation internetexplorer labourparty libdems liveblog lynnefeatherstone maps marthalanefox mashup microsoft MPs mysociety nhs onepolitics opensource ordnancesurvey ournhs parliament petitions politics powerofinformation pressoffice puffbox rationalisation reshuffle rss simonwheatley skunkworks skynews statistics stephenhale stephgray telegraph toldyouso tomloosemore tomwatson transparency transport treasury twitter typepad video walesoffice wordcamp wordcampuk wordpress wordupwhitehall youtube

Privacy Policy

  • X
  • Link
  • LinkedIn
  • 14 May 2010
    company, e-government, technology
    coi, defra, mikelittle, wordpress

    Our emergency theme helps Defra relaunch

    The biggest surprise about the transition to the new coalition administration is how few surprises there actually were. A quick tour of the departmental websites reveals, for the most part, the exact same websites that were there before – albeit a little lighter on content, and with new faces in the About Us section. It’s all gone commendably smoothly.

    But one or two departments have taken advantage of the situation to revamp their web presences: and it’s been our pleasure to assist with one of these already – with more, perhaps, to follow.

    In the run-up to Polling Day, we were asked by COI to provide cover for any ’emergency’ web building which might result from the arrival of a new administration. Steria provided a hosting environment, with WordPress MU pre-installed; and I worked with Zed1’s Mike Little to develop a theme which could be deployed and managed centrally, ideally very rapidly – but still be easily customisable for each individual site which used it.

    In the end, there weren’t any major Machinery of Government changes which required it: but Defra recognised the opportunity, and are using it as a base on which to start rebuilding their corporate website. They’ve worked with Puffbox on a few WordPress-based microsites already this year, so it’s familiar territory for them – and in truth, I think it’s been coming for a while.

    The theme is fairly plain, sober and generic: inevitably, given that we had literally no idea who might need to use it, or how. There’s a rather nice homepage carousel, managed via the WP media library; a widget-ised sidebar and ‘fat footer’; plus special page menus at the top and bottom. It makes for quite a nice little site: certainly enough to get things started.

    But whilst the design itself might not win awards, the behind-the-scenes stuff is pretty smart. We’ve enabled WordPress’s ‘custom header’ functionality on the theme: users simply need to create a graphic of predefined dimensions, upload it into WP, and it’ll be used as a full-width banner across the top (with the search form and – optionally – department name overlaid). In Defra’s case, they’ve gone for a fairly plain black logo on white; but it could have been a lot more creative if they’d wanted. When we’ve tried this in test, we’ve found it can produce quite dramatically different ‘feels’ to the theme.

    And then there’s the colour palette. The theme’s style.css file avoids defining most of the colours used on the page. Instead, there’s an options page in the WordPress backend, where you can enter the colours to be used for specific page elements: links, the ‘blobs’ in the sidebar and ‘fat footer’, and so on. These are saved in the database table of options for that specific blog only; and the custom CSS gets added to the top of each page as it gets generated. (It’s effectively an evolution of the work I did for BIS on Science & Society, but it takes the concept to a whole new level, and opens up all sorts of possibilities.)

    But of course, the most significant aspect is the centrally managed hosting environment, and the official recognition of WordPress as a suitable tool for the job. Precisely what I’ve been proposing on these pages for ages. And you know what? I think it actually worked.

  • 13 May 2010
    e-government, technology
    blogging, cabinet, twitter

    New Cabinet's online footprint

    I make it seven members of the new Coalition cabinet with Twitter accounts: although of course, some have been more personal than others:

    • Nick Clegg
    • William Hague
    • Vince Cable
    • Chris Huhne
    • Eric Pickles
    • Danny Alexander
    • Jeremy Hunt

    It’s worth noting that only Hague and Pickles have been active since polling day; and judging by one recent tweet, Pickles seems intent on maintaining pre-poll levels of activity. I wonder how many others will restart… has Twitter served its purpose, now they’ve been re-elected?

    We also have a few bloggers:

    • Jeremy Hunt
    • David Laws
    • Sir George Young

    Some of the senior Tories have made frequent contributions to the Conservatives.com site’s Blue Blog – among them David Cameron and Eric Pickles.

    The case of Sir George Young is worthy of special mention: his ‘on a lighter note’ writing goes back as far as 1999. And whilst it wouldn’t really meet the definition of a ‘blog’ – no feed, no commenting, etc – he surely deserves some credit for getting started so early. And indeed, for publishing his full constituency diary, ribbon-cutting by ribbon-cutting!

    Update: Although not strictly Cabinet, it’s also worth noting reports that the Conservatives’ head of press, Henry Macrory is to take ‘the same role at Downing Street’ (although his Twitter biog hasn’t yet been updated). Henry has been a prolific tweeter, and as you might expect from someone in his position, they’ve usually been rather partisan in nature. Can’t quite see that continuing somehow, especially not the anti-Clegg stuff.

  • 13 May 2010
    technology

    XMI mini speaker: a lifesaver

    Last Christmas, I decided to ‘crowdsource’ my wishlist. As a well-settled man in my late 30s, there wasn’t much (in the price range!) that I really wanted; so I decided to look down the various Amazon bestseller lists, and choose anything with even a modicum of appeal at the £10-20 mark. I ended up with a list of things I’d probably never have chosen. But by and large, they’ve been excellent.

    One item was the XMI X-mini II audio speaker. It’s about the size of a tangerine, with a standard 3.5mm audio jack and a mini-USB socket for recharging the internal battery. And when you unscrew its two halves, it opens up concertina-style into a speaker with a surprising amount of welly.

    I wasn’t sure how I’d find myself ever using it. But it’s proving useful in all sorts of circumstances: be it plugging into the iPod Touch for some bedtime podcast listening, or following live TV in the kitchen via the BeebPlayer Android app, or – most useful of all – plugged into a secondary PC in the office, allowing me to listen to streamed audio/video coverage of the week’s political developments.

    The Amazon write-up promises 11 hours of playback: if anything, I’d say it feels like longer. I’ve only had to recharge mine a couple of times in the past few months – although of course, I’m not using it continuously 24/7. And besides, it seems to charge up very quickly.

    For £14, I have no hesitation in recommending it very, very highly. You might not think you’ve got a use for it: but I bet you find one. Or several.

  • 4 May 2010
    e-government, technology
    government, wordpress

    Why WordPress is a good fit for government

    One way or another, it’s going to be a momentous week for UK government. A lot of people will be leaving their Whitehall offices on Thursday evening, not quite sure who they’re going to be working for – in terms of the boss, and the organisation – on Friday morning. I’ve had calls from literally all my government clients over the past week or so, just checking that I was going to be around in case of changes needing to be made. And that’s before we get into the short-term chaos of any large-scale departmental reconfiguration.

    All of which makes it a good moment for a blog post I’ve been meaning to write for some time now, on the subject of WordPress in government.

    I’ve been banging the WordPress drum up and down Whitehall since late 2007. At first, it was small tactical builds: the Darzi NHS Review in November, followed by the Wales Office in February 08. From there, over the road to Downing Street, and thence to half of central government departments – thanks in no small part to Steph Gray’s Commentariat theme, first published in February 09.

    So what exactly is it about WordPress in particular, that makes it so attractive for government in particular?

    Cuts out (the worst excesses of) procurement: In my experience, procurement teams are very good at explaining why their role is crucial, and why they need to be invited to all your meetings. But when the best available product is available free of charge, you can instantly cut out a large portion of your project schedule.

    Cheaper and friendlier suppliers: So far at least, WordPress has been the domain of the small-scale agency, or even the solo operator. We don’t have tiers of business analysts and project managers. We don’t have CMS solutions we built at significant expense several years ago, from which our product executives are trying to milk every last penny of profit. Generally speaking, the guy you speak to is the guy doing the work. No intermediaries, and minimal overheads.

    Speed of implementation: WordPress’s finest hour in government circles surely came in June last year. One Friday, two departments – BERR and DIUS – were unexpectedly forced together by a Cabinet reshuffle. By the Wednesday, and for minimal cash outlay, the newly merged web team had built a WordPress-based site for the new department. An almost incredible achievement, given the usual glacial pace of Whitehall web development. It just shows what can be done.

    Focus on content, not process: For me the key strength of WordPress is that, as soon as you log in, you’re looking at an authoring screen. If you haven’t seen many CMSes, that may sound odd. But believe me, most platforms would much rather you waded through several layers of menu before you even get close to writing some words. And that’s what policy officials and press officers are paid to do: not worry about taxonomies or systems admin.

    More than you bargained for: Time and again, I find new things WordPress can do, which I hadn’t previously known about. Things I’d never have thought to request in a tech spec; but because someone else did, or because it was a happy bi-product of something else, or because a geek somewhere fancied coding a quick plugin to do it, it’s in the package. And one day, you’ll suddenly be very grateful.

    And last, but definitely not least:

    The ‘open source’ principle: Open source does mean cheap code, but its true merit lies in what comes next. When government spends public money on IT development, the public has a right to expect to derive the maximum benefit from it – and that can mean so much more than simply getting a prettier or more efficient website out of it. In the same way that taxpayers now have a right to raw data, the same can – and I’d say, should – apply to software development. The use of other people’s code – in the form of themes and plugins – is fundamental to WordPress; and it provides an easy framework to introduce the notion of releasing HMG-commissioned code.

    If you’ve ever wondered why I’ve pushed WordPress so hard all these years, the answer is encapsulated in that last point. It represents a gentle introduction to some potentially huge concepts. I’ve seen too many people trying to pitch the concept of open source in philosophical terms; it rarely works. WordPress makes it real, and has already delivered tangible results. And we’ve only just got started.

    Footnote: this post was prompted by Dave Briggs’s reference to this video of author and blogger Aaron Brazell talking about ‘WordPress and government’ – which doesn’t really say anything specific to government. Still worth watching though.

  • 19 Apr 2010
    technology
    apple, opensource, windows

    The PC/Mac battle has ended – in a draw

    Last week, Puffbox Ltd invested in a Mac. Somehow I never quite saw myself as a Mac owner: a combination of the cost, the vendor lock-in, the slightly smug grins on Mac owners’ faces – even when the kit failed, as it seems to do with unexpected frequency, judging by my Twitter stream. But my long-serving XP desktop machine is starting to show its age, and much of my work these days is in collaboration with a Mac owner, so it seemed to make sense.

    I went for a Mac Mini: at its £510 list price, it’s roughly half the price of an entry-level iMac, as long as you’re prepared to bring your own monitor, keyboard and mouse. But I managed to find it for £477, at Dixons.co.uk; and after a bit of googling, I found a voucher code to knock a further £15 off it. Very pleased with myself.

    I’ve spent the past few days loading it up with software. First Firefox, then a few must-have extensions, giving me access to my Google-powered email and Delicious bookmarks. A suite of browsers for testing purposes: Chrome, Safari, Opera. Dropbox, to enable easy file-sharing between machines. Twhirl, my Adobe Air-powered Twitter client of choice. And so on.

    What’s been striking is that, with only a couple of exceptions, these are exactly the same apps I use most often on my XP box. (And for that matter, my Ubuntu laptop and netbook.) I needed a good code-friendly text editor, and TextWrangler got quite a few recommendations. Adium seems to be the must-have Instant Messaging client. But that was about it.

    So it’s a very unexpected experience, powering up the Mac and hearing that same startup chime, which used to herald a venture into Unfamiliar Territory. A land where right-clicking was alien. A land with strange symbols dotted around otherwise familiar keyboards. Yet nowadays, there’s no immediately distinguishable difference. You press a button at the bottom of the screen to open up a menu of programs; you click on Firefox, and you’re up, up and away.

    Is the Mac going to become my main machine, or will it remain a secondary box for fileserving and browser testing? At this point, I honestly don’t know.

    Except, of course, that it isn’t a fair choice. If you build stuff for the web, you need to test it against all browsers. And that means Microsoft Internet Explorer. And that means Windows. So like it or not, you’re stuck with Windows at some point – be it as a virtual machine, or a secondary box. Sure, there are third-party services like Litmus or IE Netrender, which send back screengrabs of your code rendered in browsers you don’t have – but I don’t believe you’ve really tested something until you’ve clicked around in it.

    Things are set to get even more complicated with the next release of Ubuntu, due in a fortnight. Like the Mac’s OS X, Ubuntu is perfectly capable of running Firefox, with its extensions, and Adobe Air, and Chrome and Dropbox. If anything, its desktop candy is even sweeter. The Mac will beat it on reliability, since Apple own the entire supply chain. But Ubuntu is at least as pretty to look it, arguably prettier… and that’s before the next release brings some new, even tastier interface themes.

    There were suggestions in the past couple of weeks that Apple’s iconic ‘I’m a Mac, I’m a PC’ series of commercials may be at an end. On reflection, it’s no surprise. It just doesn’t matter that much any more. In the wake of the open source revolution, we’re all the same.

    Except for Internet Explorer, which still sucks.

  • 30 Mar 2010
    company, e-government, technology
    careandsupport, simonwheatley, wordpress

    Live text commentary in WordPress

    I don’t usually blog about projects until after they’ve happened; but I’m going to make an exception for something that’s going to happen later today.

    For just about a year, we’ve been looking after the website for The Big Care Debate, the government’s large-scale consultation on the funding of long-term social care. We’ve had a great relationship with the team at the Department of Health, and we’ve done some fun, innovative and highly effective things: commentable documents, Facebook activity, online questionnaires, even user-submitted photo galleries.

    The consultation process is reaching its conclusion, with the publication of the government White Paper on the subject. (For those who don’t know the jargon: a ‘green paper’ presents options or starts a debate, often leading to a ‘white paper’, which is a declaration of government policy.) Oh, and as you might have noticed, there’s an election on the cards, and we’ve already had a few skirmishes on this very subject.

    When we first met to discuss plans for the White Paper publication, one idea was to ‘live tweet’ the launch event on Twitter; but I’ve never been a fan of sudden, frantic bursts of tweeting by one of the hundred-odd accounts I follow. (And indeed, I’ve ‘unfollowed’ certain people for doing precisely that.) So we reworked the plan, taking as our inspiration the undoubted success of the BBC’s ‘live text commentaries’ – seen at its best on the sports site on a Saturday afternoon, but used with increasing frequency on the news site, for set-piece events like PMQs.

    So over lunchtime, we’ll be supplementing our live video stream with a live text commentary – using ajax and some custom WordPress wizardry. It’s a very simple concept at heart. A live commentary is just a chronologically-presented series of short text chunks… just like a list of comments on a post. So that’s what we’re going to use.

    The site editor will be entering his comments via a hidden, ajax-powered comment form: and, as with any WordPress comment, he’ll benefit from features like automatic text formatting, including conversion of URLs into clickable links. Meanwhile, users will see each new comment appended to the bottom of the list, with a cute colour highlight, but without the need for a full page refresh.

    Naturally, this means a much increased workload for the web server, particularly if – as we expect – we attract a sizable audience for what looks like being front-page news. WordPress and its plugin collection can do a lot to help; but we’ve taken a few additional server-level steps to ensure all runs smoothly. All the credit for this goes to my regular collaborator Simon Wheatley, who knows a thing or two about these things, thanks in part to his work for Stephen Fry.

    There are plenty of options for running live text commentaries like this, such as the excellent CoverItLive. But there are a number of benefits to running it within WordPress: not least the fact that afterwards, you’ll instantly have a bullet-point summary of the key points at your disposal. And as we’ve been building the functionality, we’ve been getting quite excited at other ways we could use it.

    If you’re at a keyboard at lunchtime, please drop by, and let me know how you find it.

  • 26 Mar 2010
    news, technology
    bbc, firefox

    Code your own BBC News homepage

    The BBC has announced plans to switch off its low-graphic websites:

    The low graphics version of the site was designed as a low bandwidth alternative to the full website at a time when most users of the site were using slow dial-up connections. Now, most of our users are on much faster broadband connections and as a result, the percentage of users of this service has steadily declined to a current level around 2%.

    Fair enough I suppose. Except that I was one of those 2% of users. Why? – because I had it set to load in a Firefox sidebar. With one click of a browser button, I got my instant news fix. I use it constantly throughout the day.

    For obvious reasons, the full-size homepage doesn’t render especially well in a 200px-wide space; but the low-graphics version did pretty well. Not perfect, but pretty good.

    For a few days now, I’ve tried following the BBC’s advice, by switching to the mobile interface. But it just didn’t do it for me. So I’ve taken matters into my own hands, and spent the last half hour ‘coding my own’. (And most of that time was just making look a little prettier.)

    It’s a fairly simple PHP/RSS thing, with a dash of jQuery thrown in. I fetch the BBC’s homepage RSS feed via SimplePie, dress it up all pretty, then run a very quick jQuery routine to ‘zebra stripe’ the stories for easier reading. For each story, I give myself the headline, timestamp, summary – and the thumbnail image, something the low-graphic version couldn’t give (beyond the top three items).

    Why am I telling you this? Because it’s a perfect case study for the ‘raw data now’ concept. The BBC supplies the data, I bang out a hasty rendering routine based on free code… and I’ve got the service I want, regardless of what they want to do themselves.

    It’s running in my development web space; I’ve got no intention of making it public. But if you really think it would be useful for you, let me know, and I’ll maybe share the address details.

  • 25 Mar 2010
    e-government, technology
    downingstreet, telegraph, wordpress

    Telegraph calls No10 site 'a technical mess'

    Last night, the Telegraph published a piece by their head of audience development, Julian Sambles accusing the Downing Street website of being ‘a technical mess’. This damning conclusion was based on the following criticisms:

    • It wasn’t in the top search results for a few randomly-selected Budget-related search terms.
    • It doesn’t have a ‘link canonical’ tag in its code header.
    • It has a pretty curious set of ‘meta keywords’ – including ‘piercings’, ‘tattoos’ and ‘polish armed forces’. (Update: apparently not random at all – see comment below.)
    • The page templates aren’t especially well structured for SEO purposes.
    • It has inconsistent names on various external sites like Twitter, YouTube and Flickr.

    None of which, in my mind, constitute a ‘technical mess’. So it’s interesting to see, this morning, that the headline has been watered down, to mock the keyword selection.

    Some of the criticisms are valid. The site could do a few simple things to improve its SEO standing, probably taking barely a few minutes. And yes, I have trouble remembering which specific configuration of ‘downing’ and ‘st(reet)’ it uses to make up its various usernames. But some of the accusations are way over the top, and some don’t stand up at all.

    The ‘meta keywords’ criticism, for example. In the old days, search engines respected the keywords you entered in your page header as a guide to the page’s substance. But then people, possibly working in the field of ‘audience development’, began abusing them. So what does Google, with 90% of the UK search market, think about meta keywords?

    Let’s ask Google’s Matt Cutts, shall we?

    His answer: they don’t use it. ‘Basically not at all… Even in the least little bit.’ Not worth spending much time on then, I’d say.

    And then there’s the failure to rank highly for certain budget-related search terms. But would you want or expect Number10 to be a high-ranking result, when it has very little material on the subject – and isn’t the ‘lead site’ on the subject, from either a policy (HM Treasury) or a citizen-facing (Directgov) perspective?

    If you search Google right now for ‘budget’, you’ll get both HMT and DG in the top few results. That’s the appropriate outcome.

    I’m not saying there aren’t improvements I’d want to make to the Number10 site. As regular readers may know, I contributed some advice in the early days of their migration to WordPress – but I didn’t have any hands-on involvement in the build itself. If I had, for the record, certain things would have been done differently.

    PS: Thankfully, someone at the Telegraph saw sense, and dropped the ‘technical mess’ line. Otherwise I’d be forced to point out that their article page scores 88 HTML validation errors in the W3C checker, compared to the Number10 homepage’s zero.

  • 21 Mar 2010
    politics, technology
    libdems, lynnefeatherstone, seo, wordpress

    SEO as a political campaigning tool

    I’ve mentioned this before, but it still brings a smile to my face.

    One consequence of the rebuild of Lynne Featherstone MP’s website, which we launched last September, has been a marked improvement in Google performance. And it’s arguably my greatest personal triumph that if you search Google for ‘haringey council’ – the top suggested search query if you just type in ‘hari’ – here‘s what you (currently) get:

    So the first five results on a standard Google results page are: two pages from the council itself – the council’s own homepage and one of its most popular individual pages (as you’d normally expect for such a targeted query); a page from Wikipedia; a page from Directgov; and at slot number 5, LibDem MP Lynne’s automated page detailing everything that’s wrong with the Labour-run council… with a particularly arresting excerpt.

    SEO, or Search Engine Optimisation, isn’t something I typically find myself paying much (conscious) attention to. In my experience, it’s usually enough to have followed the basics of web page construction: and I’ve been coding HTML for 15 years now, so it’s all fairly instinctive. WordPress helps by encouraging you to use significant elements such as the page title – presumably including significant keywords – in both the HTML <title> and the page URL; plus there are a couple of plugins I tend to activate for all clients which help Google ranking, install instantly, and never trouble you again.

    But because it’s baked into the process, albeit subconsciously, the results are there to be seen: and will come to the fore over the next few weeks.

    Naturally, with an election imminent, MPs and candidates are looking for every possible opportunity to get their messages in front of voters and journalists. For zero extra effort, and at zero cost, we’re getting one of Lynne’s core messages in front of the tens of thousands of people searching for ‘haringey council’ each month. (According to Google’s Adwords keyword tool, 22,200 people searched for ‘haringey council’ in February 2010… far more than the 1,300 who searched for ‘lynne featherstone’ specifically.)

    Lynne is defending a relatively modest majority of 2,395 – notionally putting her in Labour’s no39 target seat. We’ve had plenty of favourable feedback regarding her website already: Iain Dale, I’m reliably informed, called it one of the best political websites he’d ever seen. But it won’t surprise you to learn that we’re looking at a couple of possible enhancements for the election campaign period. Stay tuned.

  • 20 Mar 2010
    technology

    Another version of IE in circulation. Great.

    Oh fantastic. I return from a few days holiday to discover that Microsoft has issued a ‘platform preview’ of Internet Explorer v9. So now that’s four major releases of Microsoft’s monopolistic browser in circulation: and I can’t even install IE9 for testing purposes, because it doesn’t – and won’t – run on XP, the version of Windows I currently prefer to use. (Well, ‘prefer’ is maybe a bit strong.)

    This is just getting ridiculous.

    PCWorld.com proposes that Microsoft should make IE open source – noting that it wouldn’t lead to a revenue loss, as it’s a free product anyway, and might lead to some benefits. I still find myself leaning towards the equal but opposite solution: that Microsoft should adopt an existing open source rendering engine, and compete on the basis of the functionality built upon and around it. Google did that, building its Chrome browser around the open-source Webkit originally developed by Apple – which itself had its roots in the open-source KHTML.

    It’s somewhat remarkable to see the Microsoft website heralding its 55% compatibility with the generally-accepted ACID3 standard: partial compliance is just another way of saying ‘not compliant’. The versions of Chrome, Safari and Opera (all running satisfactorily on my apparently ‘not modern enough’ machine) already score 100%. Others – Firefox, even Opera Mini and Android – are already scoring in the 90s.

    So as a result, it’s depressing to see us moving further and further away from a single global standard, for the frankly pretty mundane task of getting the right elements in the right place on the page. This is all just wasting my time, and your money.

Previous Page
1 … 6 7 8 9 10 … 21
Next Page

Proudly Powered by WordPress