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
  • 4 Oct 2010
    company, e-government
    defra, wordpress

    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.

  • 29 Sep 2010
    technology
    wordpress

    WordPress as bug-tracker

    We’re heading into the final furlong on one of the biggest projects Puffbox has ever been involved in. All being well, we should be able to talk about it in a week or so. Trust me, it’s significant.

    The stakes with this job are higher than most; so I wanted to take testing and bug-tracking a bit more seriously than usual. I had the idea the other evening to use WordPress as a centralised bug-log: and my initial thought was to use the Twitter-style P2 theme, by Automattic themselves. To be honest I’ve never really liked it, but I can appreciate its extra functionality – front end authoring, ajax comments, etc; and I’m sure we could have made it work.

    But maybe someone had done a proper bug-tracking application on top of WordPress? One quick Google later, I found that yes, within the last month someone had… and it’s truly fantastic. One of the most inspirational pieces of WordPress work I’ve seen in months.

    It’s called Quality Control, and it does everything you’d want it to do. Installation is a little bit fiddly, but nothing too onerous; set up a page to act as the ticket creation screen, define a few ‘states’ and ‘milestones’, and you’re away. Once it’s up and running, you shouldn’t ever need to look at wp-admin: everything is front-end. And as you’d expect, it’s all comment-able and feed-able, with email notifications, etc etc.

    There’s a live online demo – so rather than me explaining how it works, go and try it for yourself.

  • 6 Sep 2010
    company, e-government, technology
    wordcamp, wordpress

    A ‘WordCamp’ for Whitehall

    If you’re a civil servant working in UK central government, and you’re using WordPress (or seriously considering it), I’d like to invite you to an all-day event I’m coordinating for mid-October.

    Each January, we have the UK government Barcamps, bringing together civil servants and external enthusiasts to talk about ‘web 2.0’, social media, or whatever it’s calling itself at the time. And for the past three summers, we’ve had WordCamp UK, a gathering of the UK’s WordPress developer community. Both have been excellent fora for idea sharing, and contact building.

    In the meantime, we’ve seen steady growth in the use of WordPress within government – to the point now that it’s the natural choice for interactive applications, the expected solution for small-scale sites, and a serious option for larger-scale development.

    And so, with WordPress maturing, departmental budgets tightening and Ministerial demands increasing, it feels like the right moment to mash the two together: an opportunity for those of us already using WordPress in government to show off our latest creations, float some new ideas, and share our experiences – good and bad.

    With the generous support of the team at BIS, I’m organising a day-long WordCamp-style event for the extended family of government – civil servants and gov-centric consultants, plus a WordPress VIP or two.

    It will take place on Wednesday 13 October, at a government office in the St James’s Park area, starting at 10.30am and finishing at 4pm – giving you enough time to clear your inboxes before and after. We’ll have room for around 30 civil servants – so please, a maximum of 3 attendees per department. There will be no charge for attending, and we’re hoping to provide a decent (off-site) lunch.

    Like Barcamp, we’ll want the day’s programme to consist primarily of volunteers providing 20-25 minute presentations / demonstrations about projects they’ve been working on. So if you’re working with WordPress, please do take a slot to tell us all about it – even if it isn’t quite ready, even if it didn’t quite come off. Unlike Barcamp though, we’ll be doing our best to arrange the programme ahead of time.

    In addition to the usual suspects on the consultancy side, we’ll also be joined by a few specially invited guests – including Peter Westwood, one of the core developers of WordPress (and soon to be working full-time for Automattic).

    Book your place via Eventbrite – but please, do think about that three-per-dept limit. We’d like all interested departments to have the opportunity to send someone.

    We’ll be coordinating the planning of the event using a group on the UKGovCamp.com site, built by Steph and Dave, and running on WordPress/BuddyPress 🙂 – so if you haven’t already registered for that site, please do so. Membership of the event group will be restricted to attendees (at least to begin with).

    If you’re a supplier and you’d like to be involved, please contact me (with details of your WordPress and/or government experience). Be warned, strings are attached.

    Any other questions, feel free to get in touch via the website, or leave a comment below.

  • 27 Jul 2010
    company, technology
    ccg, ical, markpack, wordpress

    New project adds iCal feed to WordPress 3

    I’ve been working with well known LibDem blogger Mark Pack, whose day job is with PR company Mandate, to migrate the website of the Cancer Campaigning Group over to WordPress. It’s a fairly modest little site, and I was under orders to keep the design broadly as-was. But it’s got one specific feature I’m very excited about.

    Nearly four years ago, I wrote about the increasing adoption of the iCal standard for calendar sharing. With Outlook 2007 set to embrace the format, I foresaw a rush of websites publishing event data in iCal feeds, allowing you to subscribe with a single click, and then see someone else’s dates alongside your own.

    The, ahem, optimistic assessment would be that I was well ahead of the curve. Four years on, you’ll struggle to find many (mainstream) sites offering such feeds – although I’ve noticed a slight increase of late. The BBC, for example, had a feed of World Cup fixtures; the Arsenal site has a similar service for its new fixture lists, including the Reserves, Youth and Ladies teams. Why? Maybe it’s the growing prevalence of smartphones by Apple and Google, both of whom were quick to adopt the format.

    And then suddenly, the opportunity presented itself to build an iCal-enabled site of my own. The Cancer Campaigning Group’s previous site had an ‘events’ section, although it wasn’t anything special. WordPress 3.0, released just over a month ago, includes the ability to create ‘custom post types’; and I only recently discovered its little-documented ‘add_feed’ function, introduced as far back as early 2007. A little jQuery on the front- and back-ends, and we had all the ingredients we’d need.

    So I’ve written some code to create a custom post type called ‘Event’, and added it into the WP back-end interface. You enter event details just as you would enter a post or page, with a title, body text and optional excerpt. There’s a special ‘event type’ categorisation; and a pop-up date picker for simplicity and consistency.

    Then to call the calendar into a page, you use a WordPress shortcode – [calendar]. You can also specify the range (past or future), and the view (simple text list or javascript-enabled grid), plus the ‘type’ (if you’re using them). This actually gives you remarkable flexibility, only some of which is obvious on the Cancer Campaigning Group site.

    And of course – there’s the iCal feed. If you take the feed URL into your calendar app of choice, you should be able to subscribe to it. And then, as the site admin adds new events, these will simply appear alongside your own personal appointments.

    It hasn’t been easy: and to be honest, I’m not entirely confident that we’ve captured and resolved all possible issues. The biggest problem has actually been with Google Calendar: Google caches the feeds for an indeterminate period, and there’s no apparent way to force a refresh. So if there’s an issue with your code, you may not realise for several hours; and it may take a further few hours for your fix to feed through. I’m also fairly sure that the code, as it currently stands, won’t scale too well.

    So for now, I’m watching the Cancer Campaigning Group site to see what happens. If it goes OK, I’ve got a couple of much higher-profile clients waiting in the wings.

  • 2 Jul 2010
    news
    guardian, wordpress

    Guardian launches WordPress syndication plugin

    On the very day that the Times puts up its paywall, the Guardian goes the complete opposite direction – and unveils a WordPress plugin intended to gets its content out there, on as many other people’s sites as possible, free of charge.

    Once you’ve installed the plugin, and signed up for an API key, you get effectively a subeditor’s view of the Guardian’s archives. If you find a story you like, and want to republish, you save it down to your own WordPress installation, then edit and publish it as normal. It even checks stories for updates. Much neater than a DIY solution based on something like the FeedWordPress plugin, and without the potential for licensing headaches… as long as you’re happy enough to leave the credits and adverts in place.

    The blogger (or whoever) gets free, simplified access to the Guardian’s content, without licensing worries; the Guardian gets additional attention for its material, a wider spread of advertising impressions, and a PR victory over its Murdoch rivals.

    If it sounds like something you’d be interested in, you can download it from WordPress.org.

    Update: worth noting Public Strategist’s problems with the plugin: ‘Nowhere in those extensive conditions does it state that the Guardian claims the right to extend that control to the host blog.‘

  • 2 Jul 2010
    company
    wordcamp, wordpress

    Proud to be sponsoring WordCamp UK (again)

    Puffbox is proud to confirm that we will again be sponsoring WordCamp UK, the annual gathering of the nation’s users and developers of WordPress. As things stand, we’re the only sponsor to have supported the event in each of its three years of existence.

    This year’s event takes place on 17-18 July – yes, just a few weeks away; and we’re being hosted by Manchester Metropolitan University Business School – right in the heart of the nation’s computing capital (historically speaking at least!). As with last year, it’ll be a full two days, with sessions in two rooms simultaneously; and I’ll be doing a session on… er, something. Haven’t quite pinned it down yet.

    ‘Life-changing’ may be too dramatic a word; but certainly, good things have happened for me in the aftermath of both previous WordCamps that simply wouldn’t have happened otherwise. I’ve met new and interesting people; learned new things; pooled new ideas; developed working relationships; and formulated grand plans. And there’s every reason to believe that this year’s event will be similarly stimulating. That’s why Puffbox is continuing its sponsorship of the event: because, by throwing a few quid into the pot, we ensure it all happens again.

    The running order (still in development) will include sessions led by leading lights of the UK WordPress community like Simon Wheatley, Mike Little and Dave Coveney; plus at least one person, possibly two, from WP’s parent company, Automattic; and Peter Westwood, one of the core development team behind WordPress. (Regular readers of this here blog might be interested to note quite a few speakers with public sector experience, too.)

    If you’d like to join us – and you’d be most welcome, of course! – the tickets are a modest £20 each if you book now, rising to £30 after the weekend.

  • 24 Jun 2010
    technology
    wordpress

    Why WordPress 3.0 is a big deal

    The latest release of WordPress pushed the version number from 2.9 to 3.0. Usually that ‘point-zero’ means it’s a significant release: but you’d be forgiven if you ran the automatic updater, and struggled to see what was different. Sure, the admin interface is a little brighter, and a few of the labels have changed. But if you were expecting new extra-powerful menu options, you’ll have been disappointed.

    But the new release is a big deal. Among its additions:

    • the long-awaited merger of the solo WordPress product with WordPress MU (‘multi user’). Previously I’ve tended to steer people clear of MU: although an excellent product, it was definitely second priority to ‘WordPress proper’, and the usability wasn’t brilliant. Updates were slower, and plugins didn’t always work. Although there’s still a way to go on usability, I’m much happier recommending it as a safe platform – and I’ve already started hosting some of my lower-profile projects in a single ‘multisite’ installation.
    • custom taxonomies and custom content types. In fact, previous versions have had the ability to create multiple sets of tag- or category-style classifications, or tweaked versions of the ‘post’ and ‘page’ core content types – but the implementation was awkward and clunky. Based on some early experiments, I’d say they’re finally ready for industrial use.
    • custom menus, allowing you to create navigation bars containing your preferred combination of pages and tags/categories. Amazing flexibility, but be warned: most themes won’t be ready to use it (yet).
    • a new default theme which isn’t especially significant in itself, but it’s something for developers to bear in mind. Previously, if a theme didn’t have a specific file, you could rely on WP reverting to the version in the ‘default’ folder. But new installations won’t have that ‘default’ folder; and you’ll need to explicitly define a ‘parent’ theme for fallback purposes. Worth bearing in mind if you’ve lost any functionality after upgrading.

    But here’s the thing. The two most significant aspects, ‘multisite’ and custom posts/taxonomies, only become available to those prepared to get their hands dirty in the PHP code. You won’t see them, or perhaps even know they exist, until you start hacking. In the case of multisite, for example, you’ll need to edit wp-config, then edit htaccess, then edit wp-config again… not to mention the likelihood of changes to file access permissions, Apache’s httpd.conf and/or your DNS setup. Scary stuff for the vast majority of people.

    In other words, to really get the full benefit out of WordPress, you need decent coding and server admin skills. And as such, that feels like a subtle departure from the previous scenario, where a ‘power user’ could accomplish almost everything via the WordPress interface and a few plugins.

    Of course, there’s nothing to stop those power users creating magnificent sites using v3.0, without having to get their hands dirty. And indeed, there are no extra options to intimidate the nervous author or editor: the WordPress experience remains unchanged. But the addition of that extra power, underneath the surface, effectively creates a new higher echelon of ‘WordPress guy’. It becomes a platform on which you can do some very serious development, if you know what you’re doing. Graphic designers calling themselves WordPress experts might want to re-evaluate.

    On occasions in the past, I’ve worried about my business model’s longevity. All the difficult things I’d taught myself to do in WordPress kept getting easier with each new release: this time, for example, the new Custom Menu feature renders some of my smartest workarounds obsolete. But with all the new ‘developers-only’ potential, it looks like the path has a lot longer to run.

  • 24 Jun 2010
    e-government
    directgov, opensource, treasury, wordpress

    Remember to say thank-you

    A bit of a tricky moment this morning. As you might have spotted, Downing Street has launched an initiative asking ‘public sector workers’ to help the government find ways to implement the massive spending cuts proposed in Tuesday’s budget ‘in a way that is fair and responsible’. And as has become the norm for such initiatives, there’s a comment-enabled website dedicated to it, built on WordPress. A ‘hooray’ is obligatory at this point, although to be honest, that’s getting a little predictable. 😉

    In fact, it’s a return to an initiative launched by Nick Clegg last summer:

    The people who are best placed to tell us where money is not being well spent are the teachers, nurses, social workers and other public servants who work so hard day and night on our behalf. Politicians should stop talking over the heads of public servants. We need to listen to the people in the know on how we can better run public services, making sure that every penny of taxpayers’ money is well spent. That’s what ‘Asking People In The Know’ is all about.

    … but since it’s all happening again, and since the 2009 website is now giving 404 errors, one must assume it wasn’t especially fruitful.

    Anyway… If you have a look at the new website, you’ll note a startling resemblance to the Programme For Government site which I built a few weeks back. It’s very obviously a derivative work, based on my code. I didn’t build it, and I didn’t get paid for it. My contract gives the Crown the right to reuse my work; and in fact, I’m very glad they did. It’s entirely in keeping with the open-source spirit… not to mention the need to find cost savings.

    But as anyone following me on Twitter may have spotted, there was one slight hiccup. By convention, WordPress themes include details of their author. The original PFG theme notes me as its originator – obviously. But the derivative theme didn’t. My name had been deleted, and replaced with the names of two people I’ve never met or spoken to: at least one of whom appears to be a direct commercial competitor.

    I was not best pleased. I sent out a tweet to that effect: and to the credit of one of the individuals concerned, he subsequently added a line of acknowledgement. My name is duly checked, and I’m happy again.

    I am absolutely not suggesting there was any attempt to infringe my intellectual property rights, or deprive me of a deserved payment. I’m perfectly prepared to accept that it was a simple oversight. But I needed to make the point.

    Acknowledgement is the currency of the open source movement. There are communities of developers spending their free time building these tools, not to mention businesses freely handing over the fruits of their labours, resulting in you getting phenomenally powerful tools for £0.00. Saying ‘thank you’ is really the least you can do; and it’s often the only ‘payment’ that the open-source contributor receives. Don’t forget.

    Not for the first time, Steph Gray lays down a good model to follow. On every page in his Commentariat theme is an explicit credit for the Whitespace theme by Brian Gardner; and there’s a note of thanks to my regular collaborator Simon Wheatley in its style.css file.

    And in case anyone’s interested: yes, I do plan to write something for the consultation – it’s also open to ‘private sector partners working within public sector’. Now, I wonder what I might propose?

  • 9 Jun 2010
    news, technology
    independent, livejournal, telegraph, wordpress

    Another national newspaper goes WordPress

    Just to note that the Independent has switched its blogs from Livejournal to WordPress. Why? According to online editor Martin King, there was a simple reason for the move: ‘to make them better.’ Clearly a man after my own heart.

    He writes: ‘We are demonstrating that globally standard programs can free mainstream journalism from the complex bespoke set-ups of the past.’ And his colleague Jack Riley tells Journalism.co.uk: ‘WordPress is infinitely more customisable, which means that we can adapt it all as we go along. By bringing it all in-house it also means our development and editorial teams can work closely on getting the features that readers and bloggers want live as quickly as possible.’

    I must admit, I always had my suspicions that the Independent’s former arrangement with LiveJournal was driven primarily by the personalities involved, former Downing St colleagues Ben Wegg Prosser and Jimmy Leach (now back in Whitehall, of course).

    Worth mentioning too that the Telegraph has gone deeper into WordPress just recently, with the migration of its My Telegraph user community. Its blogs.telegraph.co.uk site, for journalists and commentators, moved over to WP about a year ago.

  • 25 May 2010
    company, e-government
    cabinetoffice, coalition, coi, wordpress

    Commentable Coalition plan

    Out of the blue last week, I got a call from COI: was I available for an immediate, rapid turnaround WordPress job? I was a bit startled, and detail was lacking; but since this was precisely the kind of rapid-response thinking I’ve been trying to foster around WordPress for a couple of years, I couldn’t really say no.

    As it turned out, the project in question was the Coalition Programme for Government: and the mission was to build a commentable version of it, by the next morning. COI’s initial proposal was to use Steph’s Commentariat as a base; but given the document’s structure, it didn’t feel like a good fit. Plus to be honest, I knew I’d be more comfortable working with my own code, as opposed to unpicking Steph’s – and time was too tight.

    The theme came together fairly quickly, helped in no small part by the source document’s fairly plain design – which I basically mimicked, with a couple of tweaks for better web usability. Extracting the text from the supplied PDF was excruciating, as you’d expect. But by the time I got to bed at about 2.30am, having barely left the keyboard since lunchtime, the site was ready, and my part of the work was basically done. It went live at 9:30 the next – well, technically the same – morning.

    Now… I’m going to skip over the next bit, because I’m not the right person to tell the story. Suffice to say, people came in their many tens of thousands. And although measures had been taken to handle the expected load, the platform wasn’t ready for quite that volume of interest.

    But now, a couple of days older and wiser, the site has been re-enabled: and the comments are starting to come in. This in itself presents some interesting challenges: the document is, by its very nature, more party-political than most, and the comments will be too. The civil service’s usual get-out clause – about the government being democratically elected, on the basis of its manifesto (singular) – doesn’t really work this time. Thankfully, applying the moderation policy is someone else’s problem.

    Of course it’d be nicer if things had gone perfectly smoothly on launch day. To some extent, we’ve missed the boat in terms of the immediate wave of interest; but arguably, the comments might be more considered, with the benefit of a weekend to reflect and cool off. (Well, not ‘cool off’ given the mini-heatwave, but you know what I mean.)

    And regardless of what went wrong, there’s still a great story to tell, in terms of what went right. An interactive document, designed and coded from scratch, and delivered by bedtime. That’s why we love WordPress.

Previous Page
1 … 5 6 7 8 9 … 17
Next Page

Proudly Powered by WordPress