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.
A dedicated frontend developer will make your website faster, more accessible and easier to use. This post looks at what frontend development is, and why you should hire someone in that role now.
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.
The Cyber Security team at GDS discovered it was using a vulnerable container. Here’s how the team fixed the issue and made its clean container publicly available.
The Digital Identity team at GDS has updated its Good Practice Guide on authentication and Service Manual content on checking users' identities. The new guidance provides users with clearer, more up-to-date information.
We’ve published new guidance and case studies on using chatbot and webchats, to help government organisations make the most out of these tools and meet user needs.