The UK government's design principles and examples of how they've been used.
We’re here to help build better government services, and to experiment and to try to do things differently. There’s a lot of things we won’t get right the first time, but we hope you’ll let us know when we go off track, and celebrate with us when things work out.
Defining the microservices architectural style by describing their nine common characteristics
A guide to creating inclusive digital experiences for all users.
When trying to develop a site with a consistent look and feel it’s common to develop a style guide with patterns which can be reused across the site. This lets designers easily reuse standard patterns and lets developers know how …
I am a bad blogger. I write the start to so many posts and don’t finish, but as I was walking to work this morning, listening to a song called Storm by G!YBE a thought occurred. ‘Maybe, to be more...
We're changing the policy format to better meet users' needs and get people to what they need faster. Two years ago when departments first moved onto GOV.UK we brought government policy into 1 place for the first time. We had high …
Publishing blog posts about the work you’re doing is a great way of making things open. In the early days, GDS was great at this. Working out loud and talking openly about even small changes was normal practice. It was just a thing that happened. Fast forward to 2018 and things are different. Blogs that were once active, now lie dormant – untouched for months.
I’m a digital technology specialist with extensive experience in transforming complex legacy IT, coaching technology teams as they build new digital services and coaching executives on setting the conditions for success. I advise governments, public institutions and commercial organisations on building digital capability, setting vision/strategy and leading complex transformation programmes. I was a co-founder at the UK Government Digital Service and I’ve supported the creation of digital services units around the world, including the Nova Scotia Digital Service and the State of California Alpha team.
There seems to be a common belief among front-end developers that progressive enhancement is either old fashioned or has simply been replaced by single page applications. This is a problem of perception. We’d like to explain why we use progressive …
This is the third of four posts published in the run up to the One Team Government unconference on 29 June 2017, where a bottom-up…
Technical architect, Anna Shipman, explains the reasons for choosing Cloud Foundry as the technology for Platform as a Service.
Find out about our priorities for Open Source and how you can get involved with our work to make government code open and reusable.
Point 8 of the Digital by Default Service Standard that we publish on GOV.UK says that source code for government services should be open and reusable, and our 10th design principle is "Make things open: it makes things better". We …
Paul Smith, a frontend developer at DWP, writes about why it's so important to make our work open and how we can all help make this happen.
At the Ministry of Justice, we code in the open, by default. This means whenever we write software, we make our source code available to anyone and everyone. We are strong advocates of point 8 of the Digital by Default …
...This promotes a common culture and way of working when you can see how other teams manage certain issues. Anna Shipman (left) Quite often, teams will make small improvements to...
...discovery, which leads into alpha, beta and then live. My own recent experiences make me think that while the preparation work done during 'pre-discovery' is incredibly useful, the name “pre-discovery”...
Defining the microservices architectural style by describing their nine common characteristics
<p>My notes from Museums get Mobile, 16 May 2014 in Bristol.</p>
<p>A summary of Collaborate Conference in Bristol</p>
Strategic technology leader
Strategic technology leader
Strategic technology leader
Strategic technology leader