Create guidance and assets to assist in the creation and display of 'rich' lists of items, especially in a condensed space
These can be used as content for creating and managing a list of items, but also becomes more important as upcoming layout changes will require more condensed views.
Identified as part of crud_component investigation findings and recom... (#2965 - closed)
List implementations
Where a list of items were shown there was no standard implementation. This is not surprising considering we don't have standard list implementations across the platform.
There is the opportunity to create some to improve the experience for feature teams, make the UI more predictable for users, and enable more controlled updates. However, we should be careful that these implementations should probably wider than the crud_component. For example, a project might benefit from being recognisable as a project anywhere in the product. Similar considerations should be made for other important objects, such as pipelines, people, work items, and so on.
List alignment
Lists were observed to have challenges with alignment. This, in conjunction with alignment issues often cropping up in
#is-this-known
make me think some box/stack type components could be useful to team members. This could be instead of remembering the exact combination of flex-box properties to apply combined with padding, margin and gap.Example of misalignment between items in a list
Examples of 'rich' lists of items
- Work items
- Projects
- Groups
- MRs