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.
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.
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.