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 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 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 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.
From new development processes to cultural practices, Chris gives the lowdown on how developing at GDS is different from other organisations.
The Government Digital Service aims to make technical documentation simple and easy to understand. We've updated our documentation tool to improve the user experience by adding multi-pages, collapsible navigation and more.
Find out how the GDS internal monitoring and alerting service works and how we’re improving our documentation with user research.
Catch up on all the highlights from our Build your Docs career conference.
There are many different tools and skills required for different content roles, and these requirements vary by job and over time. Writing technical documentation is a specialised role, and because of this us documenters often have to take responsibility for …
There are two big concerns government organisations have around making source code open. They want to know which subsets of the code should be kept closed and how to code in the open securely. To address these questions I’ve introduced two pieces of …