As we reflect on a successful event at GDS for World Information Architecture Day, find out how information architects’ work to classify, structure and consistently manage content is supporting GOV.UK’s ambitions.
Last quarter, a multidisciplinary team explored how we can improve the transaction (or ‘start page’) content format. A start page marks the point in the user’s journey where they move from finding out information on GOV.UK to completing a transaction …
GOV.UK was built rapidly to meet a tight deadline. The push to get GOV.UK out of beta into live, transitioning 326 government websites onto the single domain, and closing down Directgov and BusinessLink resulted in a significant amount of technical …
The GOV.UK Publishing Frontend team has created tools to help developers and designers ensure a consistent user interface across the site. We’ve already reduced the number of templates and design patterns used on GOV.UK. Now we’ve created a style guide …
The Modelling Services team recently blogged about the launch of step by step navigation. This is a new navigation pattern that shows users all the content and transactions they need to complete a service, on GOV.UK and beyond.
Over 700,000 people receive email updates from GOV.UK. These notifications help people find out when government information they’re interested in changes. At GOV.UK, we’re working on making it easier for people to sign up to receive the notifications they need, …
This post outlines 2 recent production issues on GOV.UK and how they were resolved. We’ve blogged in the past about what happens when things go wrong on GOV.UK and how we classify and prioritise incidents. What happened From around 2:50pm …
At Government Digital Service, everything we build must be accessible. It’s one of our design principles, 'This is for everyone': Accessible design is good design. Everything we build should be as inclusive, legible and readable as possible. [...] The people …
This post is about 2 incidents that affected our travel advice pages, and how they were resolved. We’ve posted before about what happens when things go wrong on GOV.UK, and how we classify and prioritise incidents on GOV.UK.
On GOV.UK, we’ve just completed our 7th wave of usability benchmarking. It’s something we do every 6 months to get an insight into whether our efforts to improve GOV.UK are having a positive impact on the overall user experience.
This post is about two severity 1 incidents caused by problems with our third-party suppliers, and how they were resolved. The incidents affected the availability of GOV.UK.