Posts tagged justinian

Week 131

I’m never quite sure how to start these things. When (as this week) I’m catching up from having missed a week I’m inclined to say something about how the situation is an indication of how the past fortnight has been. But that’s already feeling a little tired. I need to get into the habit of just writing something quick if in the midst of a specially busy/fractured week, and probably just dive in the rest of the time.

The big news of the past week is that the refresh of the Greenbelt website that we’ve been working on for the past few weeks went live on Friday. As I mentioned last time, it feels like an important step (even though much of the structure is unchanged). The festival’s really been realising over the past couple of years the volume and value of content produced and captured over that one weekend each August, and the appetite among festivalgoers for more regular content, and the prominence of the blog and the new ‘media’ section are a reflection of that. We’re also really pushing the Dispatches newsletter and have reworked the design of that, moved it to Campaign Monitor, and extended its reach to about 10x the previous subscriber list. I’m very hopeful that this work will provide a really strong base for ongoing growth.

That’s my second site launch of the month; I think I may have forgotten to mention that the Street Action site was also relaunched a few weeks back. We’re bringing news to the fore, with a stronger emphasis on photos and videos. That was particularly important as the organisation presented their key research project in parliament and was deeply involved in the highly successful Street Child World Cup over the past few weeks. There’s a lot more we want to do, but again it feels like a good step forward.

Other than those two there have been some odds and ends for Generous and a couple of other clients, but the real emphasis has continued to be on Justinian. It’s coming together as we enter the final week, and we’ve been working very successfully with SVG to lay out a relatively complex set of data in a cleanly scalable manner. Having kept half-an-eye on SVG for years it’s been refreshing to see how smoothly it’s worked in modern browsers. (We’re generating the SVG using a Rails 3 backend). It was specially good to have Ben Griffiths join us for a few days – his experience running a software team was really helpful, and he challenged a few assumptions in a manner that set us on a much more fruitful path.

So the coming week will hopefully see us wrapping up Justinian, a little more work on DAPI, and then a few days’ break. This past week I was supposed to attend the Ecampaigning Forum in Oxford, but I didn’t make it as I’d worn myself out with work (and the effects of a toddler who decided to take a few days off from sleeping). The idea of a long weekend off is very attractive.

Week 129

So. No week notes again last week. It was a week of juggling numerous projects, trying to get the month’s job list under control before diving into the project that is to dominate March. Writing here was the ball that got dropped.

One of the big jobs on the agenda has been implementing a redesign of various parts of the Greenbelt website. It was important to get it under way as it was one of those pieces which are easiest to get a feel for once you’ve made a start. It’s also quite satisfying to work on as it pulls together a number of strands that represent how the organisation has been changing and growing, but which the current site doesn’t really allow for.

Another is codenamed DAPI and is my first deployment on Rails 3. It’s a funny project in that we hope it’ll have a very short life. It’s all about transforming data that’s been stored with very little structure. Once the structured form of the data has been signed off it’ll be time to retire DAPI and build something new focussed on actually using that data. For now, it’s great to have something taking shape and to have a Rails 3 project under my belt.

The scramble has all been to make way for a larger project that dominates this month. We’re calling it Justinian and it’s been fun so far. The core team beside myself is Matt (whose project it is), Ben, James and Jenny and we’ve spent most of the week gathered around a whiteboard (aside from a field trip to the British Museum) figuring out how to represent a fairly complex set of calendar-ish data in a way that encourages both exploration and utilisation. I think we’re moving towards a good product, but it’s going to be a busy couple of weeks trying to translate it all into a functional prototype.

There’s also been a reminder this week that I need to step up the suite of monitoring tools at my disposal. god’s generally doing a good job of keeping processes up and running. Munin lets me see if servers are over capacity. But there are a lot of more fine-grained details (are search indexes updating as expected, are emails going out smoothly) that aren’t well covered by those tools or by my automated testing stack. I’m hoping that somewhere along the line there’ll be time to find a solution for that, perhaps something presenting a status dashboard?