[Design] Futureproof the LPA Dashboard for a growing number of datasets

[Ben-Hodgkiss]

Problem statement and context:

The LPA Dashboard page is growing exponentially as we add more datasets for LPAs. Whilst the design worked for 9 datasets, it is stretched at 13 when we added developer contributions. When planmaking goes live, it will move to 17 datasets and there are more in the pipeline to come in future months.

We should redesign the LPA Dashboard to account for this. This could include introducing filters to the page, grouping by collection (or similar) and hiding the datasets in an accordion or splitting out into separate webpages (a general one with collections and a more detailed one per collection).

[paris-dp]

Some very initial thoughts on this.

Filtering could offer quicker access to the dataset a user is looking for. We could also look to filter by status/collection. There are some considerations outlined here. As to not push the datasets down the page we could include 'show filters' however need to consider accessibility.

If we were to split out in to separate web pages, for the initial overview page, I am wondering if we could re-use the card with tag component used within our manage service as below;

The cards could represent collections or segments on the current dashboard. The tag could represent if this segment/collection requires attention. We could do some user engagement with a small group of LPAs to understand how users think about datasets and what would work for them to inform the design.