How we consolidated the testing landscape for GOV.UK into a small number of practical rules that are bringing a new consistency to the way we test our code.
Mark Green, a lead technical writer at the Central Digital and Data Office (CDDO), discusses the similarities and differences between technical writing and content design.
All websites run into errors. We’ve reduced our errors by over 90% and changed our culture around errors so they are identified, owned and resolved quickly.
Adding a ‘show password’ option to GOV.UK accounts looked like a straightforward task, but it was more interesting and complicated than we expected.
When a pull request failed because of an incorrect creation date, the GOV.UK Pay team investigated the cause. Here’s how they found and fixed the bug.
Rehearsing for incidents with replica environments to perform hands on investigations takes a lot of setting up. The GOV.UK Platform as a Service team wanted to see if they could get a lot of the value with a reduced amount of setup time and cost.
Frontend development is a growing role within government, and it’s a vital one, as the work is focused on the parts of government that citizens interact with most often. Iqbal Ahmed, frontend developer at GDS, outlines the main duties of the role.
GDS uses the doc-as-code approach to technical documentation, but keeping that content up to date is more of a challenge. Here’s how GDS technical writers and developers fixed the issue.
The GOV.UK Verify team at GDS needed to make sure data was protected when being shared with the eIDAS regulation framework. Here’s how they did it.
The GOV.UK Design System team at GDS has rewritten developer documentation for GOV.UK Frontend. Here’s what the team did, including how it identified what needed improving and how it tested the new content.