We’ve updated the purchasing strategy guidance in the Technology Code of Practice, to offer more advice of when to buy and when to build.
To prepare for the Document Checking Service (DCS) pilot we built out several new capabilities in the service and published our first API documentation powered by user testing.
GDS are recruiting for someone to lead on creation of the next generation of GOV.UK’s technical architecture, and to head up the community of technologists who will build this future. Find out more information about the role and how to apply.
The cross-government form-building community has grown to over 130 people and is developing resources to improve how forms are developed and used.
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.
The team behind Register to Vote explains how they improved the infrastructure it runs on, helping to modernise a service that has so far been used 37 million times.
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.
Government Digital Service is continuing work to support migration away from the Public Services Network. Here’s an update on what we’ve done so far in 2020 and a summary of next steps.
The Government Digital Service (GDS) recently hosted a remote GraphQL workshop for around 70 people from across government. Here are the main talking points from the event.
Help the government build better services by joining the cross-government community to share knowledge and resources.
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.