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.
We’re currently working to add a new point on sustainability to the Technology Code of Practice. We’re adopting a user-led and iterative approach to policy to ensure the new point is as useful and effective as possible.
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.
If you’re in the public sector and are working on APIs, find out more about our API Community of Practice and attend our upcoming event.
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.
GDS are recruiting for someone to lead on creation of the next generation of GOV.UK’s technical architecture, and to head up the community of technologists who will build this future. Find out more information about the role and how to apply.