Frontend development is a growing role within government, and it’s a vital one, as the work is focused on the parts of government that citizens interact with most often. Iqbal Ahmed, frontend developer at GDS, outlines the main duties of the role.
GDS uses the doc-as-code approach to technical documentation, but keeping that content up to date is more of a challenge. Here’s how GDS technical writers and developers fixed the issue.
The GOV.UK Verify team at GDS needed to make sure data was protected when being shared with the eIDAS regulation framework. Here’s how they did it.
The GOV.UK Design System team at GDS has rewritten developer documentation for GOV.UK Frontend. Here’s what the team did, including how it identified what needed improving and how it tested the new content.
The Cyber Security team at GDS discovered it was using a vulnerable container. Here’s how the team fixed the issue and made its clean container publicly available.
We take a look at why the GOV.UK Design System changed the element it uses for inputting numbers, making it more accessible and easier to use
Our recent Tech Talks event on interoperability and open standards featured talks from Dan Appelquist, Lorna Mitchell and Kin Lane, and we’re also hosting a couple of events on APIs and data management.
Over the past few months, us developers on the GOV.UK Custom Formats team have been trying out a new approach to software development called mob programming. Instead of individual developers working on stories separately, mob programming involves a group of …
This post is now outdated. For a more up-to-date explanation of applying to GDS please read Applying for a job at GDS: update. Over the next few months we will be recruiting for a number of roles, including developers and …