We've been working on creating a single sitewide taxonomy for GOV.UK. Find out how what this means for people across government who publish content to GOV.UK.
We're committed to blogging about every severity 1 or severity 2 incident on GOV.UK. Here's a roundup of 5 incidents that GOV.UK encountered between March and May 2018.
Users can struggle to find what they need when they navigate through GOV.UK. Topic pages will help them find what they're looking for more easily.
We've been working on improving the tools government organisations use to publish content, and the way they use data to make sure that content stays useful.
For the past few weeks, we've been working on making improvements to the GOV.UK publishing pipeline. Here's what we've done so far and what's coming next.
Over the coming months, we are working to improve sections of GOV.UK that relate to government departments and agencies (what we define as ‘organisations’).
In the first 2 quarters of 2017 to 2018, some of GOV.UK’s content designers led improvement projects with government departments on specific content areas. The goal was to improve our understanding of user needs and iterate content to meet those …
Firebreaks on GOV.UK are similar to Google’s 20% time or Spotify’s hack week. For 1 week every 3 months, teams disband and everyone is given a chance to have some self-directed time to improve GOV.UK. We’ve had 3 firebreaks now: …
This post is a roundup of 5 incidents that GOV.UK encountered between August 2017 and February 2018.
One of the objectives of our Q2 mission was to create documentation for the GOV.UK content application programming interface (API). This is a public API that allows machines to access and republish GOV.UK content. Before we started the project The …
Over three quarters of a million people use GOV.UK emails to find out when content is published or updated on the site. We used to use an external service to send these. We've built a system using GOV.UK Notify, a …
GOV.UK