Building a tool to improve our GitHub security
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.
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.
It’s part of our role as the Government Digital Service to set the standards needed for digital government to be successful.
We’ve been working with the cross-government community to set standards in APIs.
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’re working to make it easier for government technologists to access the guidance they need to buy, design and build the best possible digital services in the most efficient way…
We are pleased to launch the API data and technical standards, which is the culmination of fantastic cross-government collaboration, facilitated by GDS.