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.
How we reduced toil when managing infrastructure for 50 applications.
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.
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.
We’ve updated the purchasing strategy guidance in the Technology Code of Practice, to offer more advice of when to buy and when to build.
To prepare for the Document Checking Service (DCS) pilot we built out several new capabilities in the service and published our first API documentation powered by user testing.
The team behind Register to Vote explains how they improved the infrastructure it runs on, helping to modernise a service that has so far been used 37 million times.
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 Government Digital Service (GDS) recently hosted a remote GraphQL workshop for around 70 people from across government. Here are the main talking points from the event.
Learn more about the single sign-on solution being built for government services and how you can help shape it.
If you’re interested in jobs in this field, check out all open opportunities on the GDS careers site.