In this blog post, we explain the decision behind changing our testing requirements for Internet Explorer 11 in the Service Manual.
When the GOV.UK Pay team noticed some test payments were failing, they set about working out what was happening and how to fix it. Here’s what they did.
The Data Standards Authority and NHS Digital have published a case study about how NHS Digital used API management to build and maintain APIs more efficiently, securely and scalably.
How we improved Notify’s performance by upgrading the software we use, and what we learned along the way.
Central Digital and Data Office's new Chief Technology Officer, Dan Bailey, outlines plans for the Office of the Chief Technology Officer and the CTO Council.
How the Technology Policy and spend controls teams aim to use technology to help make a greener government.
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.
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.
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.