We started a new 2017 to 2018 roadmap in April 2017.
At the start of every tax year, we make a large number of content changes to GOV.UK. As the majority of these changes relate to increases in tax rates and thresholds, we call this process ‘uprating’.
This blog post will cover what we’ve achieved, how our biggest, most exciting challenge is yet to come, and how government needs to work together to get there.
This post outlines a recent production issue on GOV.UK and how it was resolved. We’ve blogged in the past about what happens when things go wrong on GOV.UK, and also how we classify and prioritise incidents.
We launched the beta version of the new taxonomy earlier this year, which focuses on education content. In this post we’ll go into more detail about why this new taxonomy is required, and the choices we made while developing it.
In February, GOV.UK had 2 consecutive days of errors affecting applications that utilise our publishing platform. This was a severity 2 incident.
The look and feel of the worldwide pages on GOV.UK has changed. We’ve made these changes to make things better, both for users and for GOV.UK publishers.
This post is about a severity 2 incident affecting the GOV.UK website. We routinely publish incident reports because we believe we should be open about our mistakes and share our learning. We’ve posted before about what happens when things go …
In early April we kickstarted our new 2017 to 2018 roadmap with a 2 week blitz period. As we formed new teams centralised around the roadmap missions, each team was given a single ‘must do’ task.
On 3 April 2017, GOV.UK began its new roadmap. Here’s a summary of what we delivered in the final quarter of the 2016 to 2017 roadmap, and the work that’s to follow.