Philip Wilson

More from this author

  • Automatically shipping early and often

    We're an agile team, but rather than dogmatically follow a proscriptive capital-a Agile methodology we try to hew closely to the principles behind the Agile Manifesto. Principle 3: "Working software is delivered frequently (weeks rather than months)" We're trying to...

  • Why static publishing and why Hugo?

    As we've written before, we're going to try to use Hugo for statically publishing www.bath.ac.uk. There's a nice video showing it publishing 5,000 pages in under 7 seconds, and our testing gives similar numbers. Static site serving has been big...

  • A brief overview of the technical platform for alpha.bath.ac.uk

    Our current CMS platform was introduced in 2007. It is a large, monolithic Java application which is hard to extend or customise. For the Alpha of a new CMS we wanted to base it on a popular web framework which...

  • One Hour Upgrade part 4

    The idea behind One Hour Upgrade is for each member of the Digital team to spend 60 minutes working on their own initiative to make digital communications at the University of Bath better. Things we did improved the automated response...

  • Using Rails

    After ten years of Java and PHP, the Digital team have started writing all new applications, including our new CMS, in Ruby on Rails. There are two reasons why now is a good time for us to do this. The...

  • Show & Tell, 13 February 2015

    It was a big crowd for our 5-minute talks today and, whilst Dan was drawing the pictures below, we covered a wide range of topics, from industrial-scale printing and webinars to an overview of git and shipping a new website...

  • Building alpha.bath.ac.uk

    We've changed just about everything to do with how we manage bath.ac.uk for the alpha, and this includes the underlying technology. The live www.bath.ac.uk is hosted dynamically from a monolithic Java-based CMS (OpenCms) running on Solaris servers with Oracle as...