The cross-government event covered challenges the public sector needs to think about when considering the use of blockchain, voice assistants and artificial intelligence.
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.
We changed the way fonts load on GOV.UK to speed up loading times on old devices with slow connection speeds.
We held our first Consulting Technical Architects (CTA) drop-in at the GDS offices in Whitechapel at the start August. The half-day session was attended by technologists from a range of government departments and we plan to run this drop-in clinic …
Catch up on all the highlights from our Build your Docs career conference.
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.
We recently finished a discovery to help us learn more about some of the biggest legacy problems across government.
In GOV.UK's Modelling Services team we looked at the possibility of using sticky functionality as part of our work with step by step navigation elements. Here’s what we found.
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.