How and why we removed jQuery from GOV.UK
Removing jQuery from GOV.UK was a huge yet manageable task that led to improved code and performance gains across the site. This is how and why we did this work.
Removing jQuery from GOV.UK was a huge yet manageable task that led to improved code and performance gains across the site. This is how and why we did this work.
We tested our design changes to the GOV.UK topic pages, and now we’re rolling out to all our users. Read about the A/B test and what changes we’re making.
We’ve reduced the time and effort it takes to create content on GOV.UK by improving the pasting of formatted content. Here’s why and how we did it.
We’ve improved shareable previews which makes it easier for publishers on GOV.UK to share drafts of their work. Here’s why we did it and how.
We update the GOV.UK proposition in response to changing policy and government needs. Read on to find out what’s changed.
We’ve been working to improve translations on GOV.UK to make sure they’re as accessible as possible to our millions of users in the UK and abroad. Here’s how we made technical fixes to make translations better.
We’ve made design changes to the GOV.UK homepage to improve its accessibility and make it a better user experience for the millions of people that visit it every week.
Learn why and how we updated the GOV.UK sitewide menu bar.
How we trialled and standardised a new automatic deployment process for GOV.UK, which we're now rolling out across the platform.
In this blog post we explain how Real User Monitoring (RUM) gives us an understanding of why a page is performing badly and how to fix it.