At GDS we work in quarterly missions. At the end of each cycle, teams have a firebreak to experiment and develop new ideas. Here’s what the GOV.UK Platform as a Service (PaaS) team worked on during its April firebreak.
I recently co-organised the Build your Docs career conference together with the Write the Docs (WTD) community. This was the fourth collaboration between the organisations and focused on the technical writing profession.
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.
The Technology Leaders Network (TLN) and the Digital Leaders Network (DLN) recently merged.
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.
There are many different tools and skills required for different content roles, and these requirements vary by job and over time. Writing technical documentation is a specialised role, and because of this us documenters often have to take responsibility for …