From new development processes to cultural practices, Chris gives the lowdown on how developing at GDS is different from other organisations.
Find out how the Local Land Charges team at HM Land Registry has helped local authorities in England to standardise and migrate local land charges register information to one central, accessible place.
The GDS Reliability Engineering team had to find some inventive workarounds to get the Alertmanager open source software package working on a managed container service. Here’s a detailed look at how we did it.
We give you the low-down on what tools, architecture and frameworks are being used across government, what technologists want from the frontend community and how to join.
Learn about the challenges we faced when switching to contract testing and the benefits we’ve gained by moving away from expensive end-to-end testing.
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.