We're building a new website and rather than redesigning the entire website at once, we’re creating little bits of it in iterative steps. You'll probably hear us calling this 'agile' and 'iterative' design. Laurence Grinyer explains what agile working looks like in Parliament.
When presenting findings from usability testing, we often get asked ‘how many people had that issue’. In this post, Steve Bromley explains why we don’t answer that question.
We recently launched a web interface to help applications access and query our semantic data in a triple store. Jianhan Zhu talks about what this means for our data.
Hansard are currently recruiting for Parliamentary reporters. In this post, they talk about the skills reporters need and how to apply for the job.
PDS is aware that the 650 MP constituency offices around the country don't often get the tech support they need from us. To help staff make the most of the services on offer, we've decided to create a local engagement team. Daniel Crutchfield explains what to expect from this new team.
On the 6 September last year, we turned on a new search service for parliament.uk. On the 19 January we'll switch off the ‘old service’ for all our users and we'll be fully decommissioning the service by the end of January.
We’ve been looking at the sign up process and subscription service people use to get email updates from UK Parliament. We’ve just finished our alpha phase and want to share some of what we learned.
Our Editor-in-Chief shares the editorial direction work of the content team for the year to come. As with all our strategic content work, these plans will be iterated and developed as the new website progresses.
Ray Cross started as Chief Technology Officer three months ago and he took the technology team away for a day in mid-December. He's written about how it went and what the team want to achieve in 2018.
We had a good go at sticking to our 2017 blogging resolutions, but like a lot of people, our intentions didn't quite live up to reality. So we're looking back at what went well last year and what we could do better in 2018.