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.
At the Government Digital Service we've stopped using spreadsheets and software-as-a-service tools to manage our rotas and built our own app. We've open sourced the code, so you can use it too.
Here’s what the GOV.UK Platform as a Service (PaaS) team worked on during its April firebreak.
GitHub plays a major role in the software supply chain at GDS. All our source code is stored in GitHub - mainly in Alphagov - and we work hard to make sure our repositories are secure.
Service team developers no longer need to test on Internet Explorer 8, 9 and 10 (old versions of IE) when following our ‘designing for different browsers and devices’ guidance.
This post explains how our GOV.UK Email team used load testing and code profiling when migrating to GOV.UK Notify to make sure we could continue to send out 1 million emails per hour during peak times.
When the public sector is designing services, there’s often a need to consider mobile applications. Until recently this meant creating a service for the web and then in some limited cases, creating separate native mobile apps.
We update our browser testing recommendations in the Service Manual every 6 months. Samsung Internet is the latest addition to our list to test your service in.
As technical writers at GDS we create technical documentation which includes instructions and supporting content for the products we build. We want to make our documentation consistent across all products, but also make it easier to work closely with our …