Announcements


12
Feb 12

The beta of GOV.UK

It’s been about ten days and it feels a lot longer, but recently we unveiled a rather important beta: GOV.UK. That beta is a “live operational test” of a new single-domain for government. It’s a radically simplified way for people needing UK government information and services, built in-house with a set of publishing tools that lay the groundwork for a broader platform.

This beta came out of the work a team of us did to build alpha.gov.uk, itself a deeply unusual creation for a government website: built by an in house team, ruthless in scope and relentless in user focus, and above all a prototype designed to trigger conversations. The alpha worked: it triggered good, constructive conversations, it helped us identify things that worked and others that didn’t. It paved the way for the creation of the Government Digital Service and to the beta of GOV.UK.

Around the release I’ve been writing quite a bit on the GovUK blog: an explanation of our hosting choices (AWS/EC2), there’s a colophon to list our key tools, a high level overview of how we’re using puppet and provisioning servers, a status update on the APIs we’re building. I also did a little interview for wired.co.uk, answered a few questions for O’Reilly Radar and found myself on stage (at the end of the day, having only had 3 hours’ sleep) at monkigras.

Which is really all to say that there’s not a huge amount more to say here other than to signpost all that content and to say “watch this space” cause we’re far from done!

Oh, and we’re hiring (not just ruby devs)


11
May 11

Alpha.gov.uk is GO!

Late last night I commented out the HTTP authentication settings, and Alpha.gov.uk was live.

I’ve not slept much since then, but so far everything seems to be running smoothly. Apart from my email and twitter clients which are swimming in a deluge of feedback.

There’s a quick post from me on the Alphagov blog exploring the way we’re handling geographic information and place names. A longer post is coming later in the week with an outline of the technical architecture of the site, and a few more will follow exploring more nitty gritty details.

For now, please take a look, and let us know what you think!


29
Mar 11

And so we’re revealed… AlphaGov

Last time I got round to writing weeknotes I mentioned an exciting new project. I wasn’t meant to say much about it, which is part of the reason that was the last time I got round to writing weeknotes. But today a post on the Cabinet Office digital engagement blog took the wrappers off and we can begin to talk about what we’re up to.

For the past few weeks we’ve been hard at work on an alpha version of a new “single domain” website for the UK government. From the first time I chatted with Tom about the project it was clear it was going to be something special, and an opportunity not to miss. And so far it’s certainly that. We’ve got a great team working flat out to produce something very special–though I should heavily emphasise that it will be an alpha release–for release early in May.

Hopefully the schedule will allow me to talk a bit more about what we’re working on, or at least about my contributions as Tech Lead. But that schedule’s tight, so I’m not promising anything!

In the meantime you might like to check out Jemima Kiss’ piece on the Guardian PDA blog or Simon Dickson’s piece.

You might also like to follow @alphagov on twitter, check out our team twitter list and/or follow me.


24
Jan 11

News Sauce

One of the projects that occupied the latter half of my 2010 was the build and launch of News Sauce. It’s an aggregator product that we’ve built on drupal and initially launched to pull together news coming out of the UK government.

It’s been ticking along very nicely for a couple of months now and has been very well received. Which is nice. Over the weekend there was a little surge of attention as a result of UK Gov Camp and that prompted me to write a blog entry I’ve been promising for a couple of months. So if you want to know a little more about the tech behind the site you can now find my first notes over on the News Sauce blog.

There are all manner of new features planned, and a few more “editions” to launch. I’ll try to be a little better about posting updates here.


29
Sep 10

Rails 3 Theme Support

A few months back I set out to port theme_support (my rails plugin to allow one app to serve different views under various conditions) to Rails 3. I got some basics working, but realised along the way that it was well overdue for a complete rewrite. And then I got busy with projects that didn’t use theme_support and the rewrite was left lingering.

With Rails 3′s official release a few weeks back I began getting a few requests for an updated version. Without time to do the plugin justice, I suggested people fork the project and submit patches. I’m very pleased to say that Lucas Florio took that and ran with it. The result is a new gem: themes_for_rails.

If you’re wanting theme support in a Rails 3 app, that’s the place to go.


11
May 10

has_many_polymorphs and Rails 3

I’m gradually porting a number of my older Rails apps over to Rails 3. The main motivation is a chance to really put the new version through its paces, get a better sense of how it’s working, where plugins are at, etc; but it’s also rather nice to get some of the performance improvements and cleaner code along the way.

Catapult relies on Evan Weaver’s has_many_polymorphs plugin quite extensively so it was important to be have a Rails 3 compatible version. I couldn’t find any evidence that anyone else was working on it, so I’ve forked the github project and made a few alterations. I’ve set it up to work as a gem (so I can pull in the latest version using bundler) and adjusted to fit the new rails initialization process. It’s rather hacky, but it’s working for me so far.

Evan informs me that he has no plans to work on compatibility, so I’m going to see what time I can find to tidy it up a bit more, make sure the tests are passing, etc. If anyone else is so inclined, I’d love some help with that. You can find my fork on github.


24
Aug 09

Greenbelt has an iPhone app

I’ve been watching the recent furore over Apple’s iPhone app review process with some concern. Partly, of course, I want the process to be clear, to make sense and to provide us all with good access to the apps we want. But the slightly more selfish reason was that I was waiting for the Greenbelt app to be approved for sale, hoping fervently that it would make it through in time for people to buy it before the festival.

With a little under 6 days to go, it was approved, appearing for sale on Saturday night. What’s more, they tell me they expedited the process in response to a pleading email earlier in the week, to help us meet our target.

I can’t take credit for the coding, which belongs entirely to pab. I played around with some of the code, tidied up a little javascript and provided some feedback, but he did all the hard development (and data entry) work. My role was managing the release and dealing with Apple. The app upload system is far from their finest UI work (it probably ranks amongst the worst apple interfaces I’ve used) but all in all the process worked well for us. The one rejection we did get early in the process was for a fairly clear bug that we quickly fixed.

There’s a lot more we’d like to add to the app, but it’s hugely satisfying to have it out there and it’ll be interesting to see how it affects peoples’ habits at the festival.


24
Jul 09

Talking to WordPress with ActiveRecord

As mentioned in yesterday’s announcement I’m pulling some content across from this blog (running on wordpress) into the new Ket Lai site (a merb app). I’ve found myself doing similar things a few times lately, such as on Only Connect (on which more, soon) and so have built out a selection of ActiveRecord models to help me talk to a wordpress database from a ruby app.

At Matt‘s urging (he’s been using them to move data from a legacy site), I’ve finally put those models up on github. Being a single file they arguably should have been a gist, but I’m reserving the right to reorganise them in future.

They’re far from complete in that there are lots of validations I could have added in, named scopes that would probably be handy, and loads of convenience methods that some might like, but hopefully they’ll be of use to someone and evolve over time.

(on the subject of wordpress, I’m glad to see the addition of changelogs to the plugin directory – being asked to upgrade plugins without any idea what’s changed has long been a bugbear of mine, so hopefully this will resolve some of that)


23
Jul 09

Launching Ket Lai

Ket Lai logoFor a while now I’ve been transitioning away from using the name jystewart.net for my web development work in favour of Ket Lai. The shift is partly born of a desire to separate out my work from other parts of my life (increasingly important now we’re a family of three), but mostly a recognition that I rarely work on projects solo these days–instead pulling in a range of collaborators–and a group identity is more honest to what we’re doing.

Today, thanks to the design help of frequent collaborator James Weiner I’m launching the Ket Lai website over at http://www.ketlai.co.uk. There are still a few bits and pieces we’re working on, but it’s great to have it out there for the world to see.

The site employs a variety of CSS3 techniques to give a little more visual feedback and spark, and is built on top of the merb framework (rails seemed like overkill, and personal-ish projects are usually a good chance to try something that not many client projects call for).

This blog will continue roughly at its present location, though jystewart.net may eventually get a little reorganisation/redesign-love. Naturally redirects will be used where necessary. Relevant posts are pulled across to the Ket Lai site, but this will remain a personal blog and hopefully suffer a little less from brand confusion.

So if you want to know more about the work my collaborators and I do or services we offer, www.ketlai.co.uk is the place to go. And now that it’s launched maybe (just maybe) I’ll be able to write here about a few other recent projects and interesting tidbits.


28
Mar 09

Rails 2.3 final and theme_support updates

Somewhere between Ruby on Rails versions 2.3.0 (RC1) and 2.3.2 (final) a change was made to the arguments required for one of the methods the theme_support plugin requires. I must confess I hadn’t spotted it, but github user knapo kindly sent me a message with a patch. That patch is now applied in the main repository, as are a few tweaks to the ActionMailer integration to better handle multipart emails. You can get the new version from github.

Perhaps more significant than those small patches is that I’ve now pushed up a new rails app for use in testing theme_support. The tests are a series of cucumber stories, and the app is very barebones designed entirely to test the various features. I could do with tightening up the way the test app and the main plugin repository are connected, but it’s a start and has been very helpful with the aforementioned patches. Any improvements to the test suite would be much appreciated. You can, of course, find it on github.