Add Namespace catalog to the left navigation
Proposal
The component catalog is a new ultimate solution we would like to introduce in the coming quarter. The goal of the CI/CD pipeline components catalog is to make reusing pipeline configurations easier and more efficient. Providing a way to discover, understand and learn how to reuse pipeline constructs allows for a more streamlined experience. Having a CI/CD pipeline components catalog also sets a framework for users to collaborate on pipeline constructs so that they can be evolved and improved over time.
This catalog will have 2 flavors
- Namespace catalog - scoped per organization (namespace)
- Community catalog - single instance across all organization (similar to GitHub action marketplace, or Circle Ci orbs)
This discussion should revolved around the Namespace
catalog only
Latest findings - Update Jun 10th
The explore tab is not a suitable location for a Namespace catalog (it might be suitable for an instance-wide setting or a community
catalog but that's a different conversation as we are months away for having such a solution)
The explore
is not scoped to a single Namespace, as it takes you to see all the projects you are a member of.
This means that as a user I can't see the catalog scoped to a namespace, and as mentioned above Namespace catalog should be scoped to a namespace
See the discussion at #413409 (comment 1425432348)
Video explanation in https://youtu.be/_jVpkGLTuTQ
Research findings - Updated on April 11
Based on the findings of the recent unmoderated test about the private catalog https://gitlab.com/gitlab-org/ux-research/-/issues/2401, 7 out of 10 participants found this information on the project navigation under the Build menu. We are aiming to have a private components catalog under the CI/CD
menu (in the new sidebar, under Build
) and it should be visible only for the Ultimate customer.
Additional resources
- Business case
- Direction page
- Competitive analysis walkthrough - Learn how our competitive build similar solutions
- Opportunity canvas and the recording - Learn more about the business case
- Opportunity Canvas Follow-up Issue - Follow ups and final decision from the opportunity canvas
-
Catalog Problem Validation Research
- Problem validation insights https://dovetailapp.com/projects/16xmTsa96SJ4iAukqcude4/insights
- Solution validation insights https://dovetailapp.com/projects/6Ws3qZW1GR8Dc7nRLaddMg/insights
- Catalog epic
Checklist
-
Add relevant information to the issue description detailing your proposal, including usage and business drivers. -
Follow the product development workflow validation process to ensure you are solving a well understood problem and that the proposed change is understandable and non-disruptive to users. Navigation-specific research is strongly encouraged. -
Engage the Foundations Product Manager for approval. The Foundations DRI will work with UX partners in product design, research, and technical writing, as applicable. -
Engage the Foundations team to ensure your proposal is in alignment with holistic changes happening to the left side bar. -
Consider whether you need to communicate the change somehow, or if you will have an interim period in the UI where your nav item will live in more than one place.