Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Help users understand the history of a document, object or process by showing them a sequence of timestamped events.
Variants of this pattern are already in use in multiple internal services at Home Office, DWP and HMCTS.
created this issue from a note
in GOV.UK Design System Community Backlog
Jan 15, 2018
At the moment it’s very much just trying to get people sharing things that fall outside known patterns. We’re trying to avoid trying to define patterns and components for the moment because it often ends up so low level that everything just grinds to a halt whilst people argue over what is a pattern etc.
So, the design examples repo is our attempt at just trying to get people sharing designs. We’ve created an issue template to ask some simple questions such as: ‘Which service are you using this on?’ and ‘Has this been accessibility tested?’. The aim is to get a bit of consistency of things that solve a problem and give people a bit of reassurance as to how mature a design is, rather than trying to define anything as a pattern just yet. In time, if enough people use it and there's enough research behind it, maybe then we try and define it as a pattern.
Alongside this we had our first meet up about it last month. We figured getting everyone in a room once a month might help keep momentum up.
At the meetup, we showed the GitHub repo and how to add screenshots to it. We also did a workshop where people brought along examples of a ‘search feature’. We found we had 5 just at the meetup, and I’m aware of another 2 or 3. So we have lots of people reinventing the wheel each time.
The workshop was to try and define what exactly it was it was doing and to see if we could try and compile our 7/8 different versions down to maybe 1 or 2. We found we can probably start with 2. We had a lookup, which wasn’t really a search. It was putting in a national insurance number and getting back exact matches. If there was no match there were no results. Then, there was the fuzzy matching search a bit like Google. Where if you get no exact matches it returns similar things.
So, the next step is to try and refine a decent version of both of these so anybody in future doing a search or lookup has a place to start. We are also planning the next meet up and hoping to do some deep dives into services to see if we can start to identify more of these things that are similar across services.
Here are the slides from the meet up https://docs.google.com/presentation/d/1xGiKEqWXGRobEH32TfN6wGnBG8t4ygOavOS0_8j3iDM
And @htmlandbacon also wrote a blog post about it: https://medium.com/@colinoakley/thoughts-from-dwp-digital-design-patterns-meet-1-4de66bbccaee
If there is anything else I can help with just give me a shout =)