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

  • ,
    , , ,

    WordCamp UK 2009: seriously good

    My session at WordCamp UK 2009

    I can’t underline enough how enjoyable, educational and thought-provoking this weekend’s second WordCampUK was: over 100 people, including a large local contingent, gathering in Cardiff Bay for two packed days of WordPress talk, a bit of food, quite a lot to drink, and nowhere near enough sleep.

    Last year in Birmingham, it felt amateur – and I mean that in both the positive and negative senses of the word. It was a bit like a first date. Fun and exciting, with some unforgettable moments, and clearly the start of something special – but acutely embarrassing in places. (Oh, and an incredibly vicious Twitter backchannel.)

    All so different this year. Bigger and better presenters with bigger and better stories to tell, and a definite sense that we’re shifting up the gears, really quite quickly. And the Twitter chat was much nicer too.

    The highlight, inevitably, was the appearance of Mr WordPress himself, Matt Mullenweg. Charming, charismatic, cool and – I’m not ashamed to admit this – cute. Rather than give his almost traditional ‘State of the Word’ lecture, he took questions from the floor… and it was inspirational stuff.

    I’ll take away a few specific things from what he said. His description of WordPress as a platform comparable to Windows or MacOS, given the number of plugin ‘programs’ written for it. His perfect ease at calling WordPress a CMS. His unexpectedly complimentary tone regarding Drupal. But most of all, the purity of his philosophy, and the strength of his commitment to it. I expected to detect a sharp business edge to his remarks (cf Zuckerberg); in the end, I was relieved not to.

    We had many references, particularly through day one, to government use – and indeed, Matt confirmed that the UK and Brazil are the two countries where government buy-in is highest. So no pressure on me, then, for my Sunday lunchtime slot on the government picture – lessons learned from the number10.gov.uk launch, and the many ripples spreading out from that (which I’ll write up separately). I was my usual bouncy, passionate self, and it seemed to go down well: somebody described me as the WordPress community’s Jamie Oliver, which I’ll take as a compliment. Pukka!

    Whereas last year saw a lot of people presenting their hobby sites, this year seemed to be entirely professional examples. But it didn’t stop speaker after speaker handing over their tips and advice – to put it another way, their trade secrets. So whilst WordPress is unquestionably becoming a serious product, and a serious business, it remains a supportive community. It’s Us versus Them – with Them being different things or people at different times. (I should have made a list.)

    I’ll admit, I went to WordCamp looking for an answer to a difficult question. I’m making my living from WordPress, and I can see a proper industry starting to take shape around it: so what should I be doing about it?

    One answer was Matt Mullenweg’s hippy philosophy, without which we wouldn’t be here in the first place, of course. Betfair’s Nick Garner, meanwhile, framed it all as a commercial opportunity, with the proposal for a ‘WordCon’ spinoff event pitching WordPress (and us as WordPress experts) to corporate clients. It led to some, ahem, heated debate.

    Maybe Matt needs to grow up. Maybe Nick totally misses the point. Maybe they’re both right in different ways. My question remains unanswered, but I’m all the more convinced that it’s the right question to be asking, and the right moment to be asking it.

    Pic by Mark, @cMadMan: that’s me at the front, waving a can of Red Bull Cola at the good people of WordCamp.

  • ,
    ,

    Govt depts in no rush to upgrade from IE6

    Former e-government minister Tom Watson has tabled a string of Parliamentary Questions, asking various government departments what plans they have to upgrade their default web browser from Internet Explorer v6. The answers are starting to come in, and they aren’t pretty.

    … no plans to change …

    … in the process of reviewing the options…  no decision as to which web browser the Department will update to or when any update might take place …

    … currently reviewing our options …

    … the upgrade to IE is planned to be completed prior to Microsoft ceasing to support IE6 …

    But the most depressing response so far comes from the Ministry of Defence:

    The Ministry of Defence (MOD) is currently implementing the Defence Information Infrastructure (Future) (DII(F)). DII(F) will, once delivered in full, incorporate around 140,000 terminals supporting some 300,000 users at over 2,000 defence sites worldwide, including on ships and deployed operations. DII currently uses Internet Explorer 6 and at the current time does not have a requirement to move to an updated version.

    So maybe it’s worth running through precisely why it’s such a bad thing that government departments aren’t being systematically moved off IE6. It’s partly technical, partly design – but mostly, I think, it’s the symbolism of departments refusing to move forward.

    On the technical front, IE6 has security holes that just aren’t being fixed. Analysts Secunia say there have been 10 security alerts in the last year; and that there are 21 unresolved problems. Now to be honest, day-to-day, this probably doesn’t amount to much more than a theoretical risk, but it’s a risk nonetheless.

    It’s also slow: IE8 is twice as fast at running Javascript, whilst the latest versions of Firefox and Google’s Chrome are at least 4x faster. This hasn’t mattered much until the explosive growth of Ajax techniques in the last year or two. But now, a lot of the revolutionary ‘web 2.0’ sites simply aren’t usable on IE6. And with more and more stuff happening in the web browser (‘G-Cloud’?), it’s only going to get worse.

    Then there’s the design issues. Most web design these days is (or should be) based entirely on CSS, Cascading Style Sheets. And frankly, IE6’s handling of CSS is appalling. Ask any web designer, they’ll tell you the same story:

    From GraphJam

    If you follow the W3C rules, designs will generally work perfectly (ish) first time on Firefox, Chrome, Safari, and in all fairness, IE8. Then you hold your breath, and test it in IE6… and goodness knows how it’ll come out. Things might be the wrong size, or in the wrong place, or might not be visible at all. The layout you spent weeks crafting could be a complete mess. You then have to spend ages bastardising your code, often breaking those W3C rules – and sometimes defying all logic! – to make it come out right, or near enough, in IE6. It takes time, it costs clients money, and it makes designers sad.

    In reality, everyone in the industry knows this. We’ve been living with it for long enough, and we’ve all got our various workarounds. We factor the IE6 delay into our timescales. We know not to be too ambitious sometimes, ‘because it’ll never work in IE6’.

    But the reason it’s such a sore point for us government hangers-on is that IE7 (released in October 2006) is free of charge, and Microsoft’s formally recommended course of action is to upgrade. Dammit, that’s what HM Government itself tells people to do. Yet departments are quite happily burying their heads in the sand – ignoring the sound technical, financial and qualitative reasons for upgrading.

    They think doing nothing is the safe option. They’re wrong.

  • ,

    'Cash for your old phone': it works!

    fonebank100It turns out that not all bankers are greedy b*%@!#s. Having gathered quite enough dust in an upstairs drawer, I finally decided it was time to get shot of a couple of old mobile phones I’ve had lying around for (literally) years. Coincidentally, both were Windows Mobile smartphones: an Orange C500 and a T-Mobile MDA Pro. Both had served me well: y0u couldn’t argue with the C500 in its time, a candybar smartphone which did it all; the MDA was really too big to be a phone, but it found plenty of use as a pocket laptop.

    Having checked a few of the phone recycling sites, I settled on Fonebank.com: not solely because they were prepared to give me the best prices, but because their website seemed more professional than some others – it’s easy to imagine how you could easily get ‘done’ by one of these sites, deciding your phone wasn’t quite in the mint condition you claimed.

    The phones were duly bubble-wrapped, and sent to a Freepost address – thus avoiding the hassle of paying postage by weight and dimensions. A week later, and I’ve got a genuine, actual cheque in my hands. So I’ve now got a bit more room in my drawers, and enough cash to pay for a half-decent meal out. On that basis, I’ve got no problems recommending you give your old mobile a new lease of life through Fonebank, either in a less developed market, or in bits. And if you do, quote the referral code RkVnxJ – it might be enough to get us our pudding too.

  • , ,

    Why the fork does the BBC need its own jQuery?

    Of course it’s good news that the BBC’s in-house Javascript library, Glow has been released as open source. It’s a very respectable chunk of code, with some quite nice built-in widgetry. But why on earth should the BBC have its own Javascript library in the first place? Its ‘lead product manager’ – itself a worrying job title – justifies its existence as follows:

    The simple answer can be found in our Browser Support Standards. These standards define the levels of support for the various browsers and devices used to access bbc.co.uk: some JavaScript libraries may conform to these standards, but many do not, and those that do may change their policies in the future. Given this fact, we decided that the only way to ensure a consistent experience for our audiences was to develop a library specifically designed to meet these standards.

    They’re clearly sensitive to this question, as there’s a whole section about it on the Glow website itself, specifically referencing my own current favourite, jQuery. ‘On reviewing the major libraries we found that none met our standards and guidelines, with browser support in particular being a major issue,’ they explain.

    So why not contribute to something like jQuery, to make up for its deficiencies? Isn’t that the whole point of open source? ‘Many of the libraries had previously supported some of our “problem” browsers, and actively chosen to drop that support… Forking an existing library to add the necessary browser support was another option, and one that might have had short term benefits. However, as our fork inevitably drifted apart from the parent project we would be left with increasing work to maintain feature parity, or risk confusing developers using our library.’

    I’ve written here in the past in praise of the BBC’s browser standards policy, and I stand by that. But I’m afraid I’m not buying this defence of their decision to reinvent the wheel – and, it must be noted, ending up with results remarkably close to jQuery. The best argument seems to be the risk that libraries which currently meet their standards might not in the future; or that they might have to do work to keep a fork in sync. And even if that should happen, the worst case scenario is that they’d have to churn out a load of new Javascript. Which is what they’ve chosen to do anyway.

    Plus, crucially, this isn’t about a bunch of geeks directing their spare-time volunteering efforts in one direction, rather than another. These are people being paid real money, taxpayers’ money, to do this, at a time when the BBC is supposed to be trimming its ambitions. If they’re at a loose end, perhaps they might want to address the News homepage’s 416 HTML validation errors, and abandon the ‘table’ markup.

  • ,
    , , ,

    Telegraph moves its blogs to WordPress

    It’s a sign of how far WordPress has come, that I find myself noting the Telegraph’s transfer of its blogging platform to WordPress purely because I feel I should… and not because it’s especially exciting. I mean, if you were going to set up a large-scale public blogging community, why on earth wouldn’t you use the world-leading, zero-price tag product?

    The newspaper media group’s new blogs editor, Damian Thompson is buzzing with excitement at the potential which this move opens up. Among the ‘immediate benefits’ he highlights: faster operation, easier commenting, better integration with the wider site, even a Twitter element. (I’d add a few others myself, all available instantly with a bit of URL hacking.) But he’s right to recognise that the switch won’t be immediately popular – and guess what, the majority of the 200+ comments on his introduction post aren’t positive. Yeah, we’ve all been there.

    Most of the work, I understand, was done by the Telegraph’s in-house team, with some assistance from my fellow WordCampers (and technically, I suppose, competitors) InterconnectIT. The firm’s director, Dave Coveney says they’re already working with another newspaper group and a magazine publisher. He’s clearly seeing the same momentum I am; there’s certainly no shortage of interest in WordPress just now.

  • ,
    , , ,

    Tim Berners-Lee: the celebrity we need?

    When Andrew Stott was appointed Director of Digital Engagement, I commented that it wasn’t the ‘rock star’ appointment many of us had been led to expect. Well, the ‘rock star’ appointment came through yesterday, with the news that Sir Tim Berners-Lee as the government’s ‘expert advisor on public information delivery’. The Director position required evidence of having ‘run a public facing web site of significant size’: well, I guess TBL qualifies, having run the entire web at one point. 🙂

    This is meant to send a loud and clear signal to the civil service: raw data now. And I couldn’t agree more; see this post, for example, from 2008 about ‘API-first publication’, in the context of the 2011 Census. But I think it’s more about how that signal gets sent.

    The Cabinet Office press release says:

    He will head a panel of experts who will advise the Minister for the Cabinet Office on how government can best use the internet to make non-personal public data as widely available as possible. He will oversee the work to create a single online point of access for government held public data and develop proposals to extend access to data from the wider public sector, including selecting and implementing common standards. He will also help drive the use of the internet to improve government consultation processes.

    It reads like a rather hands-off, committee-based kind of role. And whilst that wouldn’t be a bad thing in itself, I wonder if it’s what The Machine really needs from him. What’s the question, to which ‘Sir Tim Berners-Lee’ is the answer?

    I don’t think we particularly need the advice on standards; and I don’t know that TBL will be able to tell (checks the post-reshuffle situation) Tessa Jowell how to organise data publication processes inside the typical Whitehall department. But what he will be able to do is intimidate persuade those people who always seem to block the initiatives which have already gone before. He may have more success saying the exact same things many of us have already been saying for some time, because of who he is.

    Stuart Bruce, who knows a thing or two about PR / technology / the Labour Party responded thus on Twitter: ‘Opening access to government data YES! Well done. But Tim Berners-Lee? Isn’t that just like Sugar, yet more cult of celebrity.’ Maybe so. Probably so, in fact. But it may be exactly what we need.

  • , ,

    Making bbPress speak proper English

    Today’s focus has been mostly on bbPress, the discussion forum cousin of WordPress. I’ve played with it a few times in the past, but never yet had cause to use it properly or professionally. But when a call came from a client last week, asking to forum up an existing WordPress-based site, I ignored the advice of Tom Loosemore and set to work. Not feeling brave enough to use the v1.0 release candidate, I downloaded the latest stable v0.9.x version, and had it up and running in next to no time.

    As it’s my first time building a bbPress theme, I’ve restricted myself almost entirely to CSS, and letting bbPress fall back on the default PHP code templates. As with WordPress, if your theme doesn’t include a file for a particular purpose, bbPress uses the equivalent from the default theme (‘kakumei’). But if you do that, you’re reliant on the peculiarities coded into those default templates… including, as it turned out, their Americanised spelling.

    Unlike many forum apps, bbPress doesn’t have many bells and whistles – overall, that’s a good thing in my book. But one of the few extras it does offer is the ability to mark certain discussions as a ‘favorite’. You can view these as a ‘personalised homepage’, or follow their updates with a unified RSS feed. Fantastic, except if you’re building a site for a UK audience – who would much rather save some favourites. So for a while this morning, I found myself unexpectedly creating a new language pack for bbPress. This consisted of:

    • Downloading a .pot file from Automattic.com’s servers. This is effectively a big list of all the individual system messages used by the software (in the default US English).
    • Installing the open-source poEdit for Windows, which shows you all these messages in a big list, and asks you to enter equivalents in the foreign language of your choice (in our case, ‘en-gb’) alongside. I ran a search for ‘favorite’ and changed all matching messages to use the proper spelling. 😉 Watch out for phrases with more than one use of the word.
    • When you save your amendments, you’ll end up with a file called en-gb.mo. If you’ve only changed the references to ‘favorite’, it’ll only be 2 or 3 Kb in size. You’ll need to create a languages folder within the bb-includes folder of your bbPress installation, and put the .mo file in it.
    • Then you’ll need to edit the bb-config.php file at the root level of your bbPress installation. Look for a line that says define(‘BB_LANG’, ”); and add en-gb in between the second pair of quotes.
    • And that should do it. When WordPress tries to produce a page based on the default templates, it will scan through your en-gb translations list, and in the few cases where it finds a match, it’ll replace the Americanized default with your Queen’s English alternative.

    This reminds me of an idea I had a while back, to produce a ‘corporate English’ language pack for WordPress, replacing blogger jargon with text which might be more familiar to press officers, marketing people, journalists, or whoever. It might still be worth doing; although in the meantime, the word ‘blog’ seems to have lost its overwhelmingly negative connotations.

  • , ,
    , ,

    Nick Clegg's off-the-shelf redesign

    NickClegg.com May09 500

    There’s a new look to NickClegg.com, ‘the official Leader’s site for the Liberal Democrats’, powered – as noted previously – by WordPress. And it isn’t yellow, not in the slightest. In fact, it took me quite a while even to spot the party’s bird logo, concealed in each instance behind signatures or other graphic elements.

    This isn’t like any Liberal Democrats web design you’ve seen before… because basically, it isn’t a LibDems web design. It’s an ‘out of the box’ installation of the (free) Revolution Office theme for WordPress… seen here in its raw form.

    Of course, on one level, this is another reminder of the power of WordPress. Redesigning your entire website is as simple as finding a theme you like, downloading it, and pressing the ‘activate’ button. A few minutes tweaking the settings, and you’re done. So quick, so easy, so cheap. Plus, depending on the theme author, a guarantee (of sorts) that your site will keep working, no matter what changes happen in forthcoming WordPress upgrades.

    But I’ve never felt entirely comfortable with ‘off the shelf’ design like this. As soon as I understood how, I stopped using third-party themes, and started coding my own. Several reasons for doing so, I think:

    • A need to understand what’s happening under the hood… in case something goes wrong, and you’re called on to fix it. I don’t think you can get that from ‘plug and play’ theming.
    • Something instinctive about branding. Your brand identity is meant to be a representation of you, what you do, and why you do it. Deep down, I don’t really believe it can be ‘you’ if you’re just pouring yourself into someone else’s mould. It can’t have soul unless it started from scratch.
    • Total customisability. No matter how good an off-the-shelf theme might be, I can’t believe it’ll cover every possible requirement a client might throw at you. So you’re going to end up getting your hands dirty with code anyway; and if it’s your own code in the first place, it should be much easier. (See point one.)
    • Fraud risk. Yes, you use off-the-shelf because it makes it much easier for you. But equally, it makes it easy – far too easy – for someone else to grab a ‘lookalike’ domain, download the same theme, and build (in effect) a ‘phishing’ site.

    (The only exception is the production of sites based on Steph’s Commentariat theme: as I’ve described before, I personally think it’s important – for now at least – that these sites look deliberately similar, to make a point about code re-use in HMG.)

    Maybe I’m being too precious about this. On low-budget, low-ambition projects, an off-the-shelf theme will probably be more, much more than adequate. You can have a website with top-notch functionality up and running in, let’s say, an hour. Client is happy, designer is off to the pub.

    Ultimately, I think it comes down to how you see your business. Companies make money by selling lots of something cheap, or a few of something expensive. You can churn out lots of identikit sites for lots of people: that’s a perfectly valid business model, albeit pretty intensive on the sales side. Alternatively, you can try to make each one special. Puffbox opted for the latter. And so far, we’re doing OK out of it.

  • ,
    , ,

    The lady's not for YouTube-ing? Says who?

    With the long Bank Holiday weekend behind us, Sunday’s Observer piece by Hazel Blears already seems like a distant memory. ‘YouTube if you want to,’ she wrote – somewhat provocatively, on the weekend we recall Margaret Thatcher’s ascension to Downing Street. Quite a soundbite, especially considering her reflection in that same piece that: ‘No government after 12 years in office can compete on slick presentation and clever soundbites.’

    Having finally read the piece, it seems much more reasoned and balanced than the coverage would have you believe. The opening clause – ‘When Gordon Brown leads Labour into the next general election’ – wasn’t sufficient to stop ludicrous leadership speculation. Nor were the words ‘I’m not against new media’, nor indeed her previous statements on the subject, enough to prevent people seeing it as anti-YouTube per se.

    Blears’s fundamental point, surely, was this: ‘Labour ministers have a collective responsibility for the government’s lamentable failure to get our message across… We need to have a relationship with the voters based on shared instincts and emotions.’ She does not say that YouTube – or any other new media/social tools – aren’t part of this. What she says, correctly, is that they are ‘no substitute’ for proper, face-to-face politics.

    ‘We need to plug ourselves back into people’s emotions and instincts and sound a little less ministerial and a little more human,’ she writes. I couldn’t agree more. Talking to people in the street is certainly one way to do this. Talking to them online, via a blog or Twitter, is another. Talking down a camera lens can also work. But some methods will work better with certain audiences – and for certain politicians. Not all politicians are gifted writers, or on-camera performers.

    Hazel Blears is hitting the nail squarely on the head here. In a year’s time, presumably, we’ll be asked to give this government another 4-5 years in office, on top of the 13 they’ll already have had. Why should we? They need to find a good answer to that very simple question, fast – and then get it out via every channel at their disposal.

  • ,

    WordPress in UK government: an informal audit

    I thought it was about time I compiled a list of all the UK (central) government web projects I know of, which use WordPress. Partly because I’m meeting some people during the week to talk about it; partly to start preparation for the session I’ve volunteered to give at July’s WordCamp UK. This is off the top of my head, and I’m sure I’ve missed a few obvious examples: please leave additions and amendments in the comments.

    I’m only looking for live sites: I know of several more projects ‘in the works’ (and am always keen to receive tipoffs!). I’ve noted those built on Steph’s open-source Commentariat theme with an asterisk.

    HEALTH

    DFID

    BIS

    BERR (now BIS)

    UKTI

    DIUS (now BIS)

    JUSTICE

    DEFRA

    SCOTLAND OFFICE

    WALES OFFICE

    CABINET OFFICE

    10 DOWNING STREET

    MINISTRY OF DEFENCE

    COI

    ORDNANCE SURVEY

    ROYAL NAVY

    LAW COMMISSION

    PARLIAMENT