Design: Explore ways to represent the data in the CI/CD Catalog index page
Overview
- Relevant Slack conversation: https://gitlab.slack.com/archives/C04CRLZSXMW/p1696501428709299
Since we will have more component types available in the components repositories, it is important to assess the scalability of the current design of the index page.
Considerations
- A single components repository will contain multiple components spanning various types (e.g., templates, steps, and jobs).
- In the longer term, we may anticipate having components such as project templates, container images, etc.
- Each component will have different inputs and in the future outputs - serving as configuration parameters.
- We were discussing in the past to allow assigning
tags
to components making them much easier to search. Example tags could be:docker
,docker-build
.
Current implementation
The existing view displays one components repository per row.
Questions
- Is it currently easy for users to locate specific components?
- What advantages could users have in using the search within the CI/CD Catalog rather than the global search? How can we enhance this experience?
Design explorations
Checklist
-
Refine the proposals -
Review with the designers, CI/CD UX team - November 16, 2023
) -
Review with the PA team -
Incorporate feedback
Next steps
Conduct solution validations: https://gitlab.com/gitlab-org/ux-research/-/issues/2772+
Edited by Sunjung Park