In this blog post, we explain the decision behind changing our testing requirements for Internet Explorer 11 in the Service Manual.
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.
Government Digital Service is continuing work to support migration away from the Public Services Network. Here’s an update on what we’ve done so far in 2020 and a summary of next steps.
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.
Help the government build better services by joining the cross-government community to share knowledge and resources.
The GOV.UK Verify team at GDS needed to make sure data was protected when being shared with the eIDAS regulation framework. Here’s how they did it.
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.
We’ve enabled HTTP/2 on GOV.UK to help improve the site’s performance. Here we look at what HTTP/2 is, how it improves performance, and the impact it has had on our users.
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.