The standards that underpin GOV.UK Verify have always been open but we started coding as a private project. Here’s a recap of our journey to coding in the open.
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 hosted an event for developers as part of the Global Day of Code Retreat. Find out what we did and why we set them an impossible challenge.
The GOV.UK Pay team has made significant performance improvements by using the GOV.UK Design System. Find out what our migration process was like and how your service can benefit too.
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.
The cross-government event covered challenges the public sector needs to think about when considering the use of blockchain, voice assistants and artificial intelligence.
The cross-government open source meetup addressed common barriers to coding in the open, from hacking fears to licensing confusion.
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.
Our second CTA drop-in session focused on agile architectures and how we can use these across government.
If you’re interested in jobs in this field, check out all open opportunities on the GDS careers site.