We recently blogged about turning off the old search. We then worked on creating the global search component and this blog post is about what we did from a technical perspective and why.
Gavin Berman, one of our business partners, explains what business partners do and how it works in Parliament.
Our website product teams have people doing a variety of different roles. This gives us a good mix of people with the right skills to build what users need. In this post, we take a look at the part content designers play.
We recently launched an online process for petitioning against a hybrid bill after receiving hundreds of paper petitions against a recent bill. Sarah Purssell has blogged about why this was a good opportunity to develop this as a digital service.
The user engagement team is one of the largest in PDS. Despite being so many, there's probably a lot of people who don’t actually know who we are or what we do. That's what this blog post is for.
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.