### Overview A core challenge to solve is discovering all resources that can be used in GitLab pipelines. We need a single view, where a user can filter components that are available in the entire system. ### User stories 1. When creating pipelines, I want to easily select and reuse things in my jobs from my editor. 2. I expect to find `CI/CD Catalog` in `Explore` 3. When using templates and components, I want to easily see when components are `GitLab Official`, `Community` components ### Proposal Create a Single catalog view with filters on components: - All - list of all components - in public/internal/private and instance-wide. - [Pages & Navigation](https://gitlab.com/groups/gitlab-org/-/epics/11841) to access Public Catalog from gitlab.com - [Search and filter](https://gitlab.com/groups/gitlab-org/-/epics/10918) capabilities to find components in Public Catalog on gitlab.com - [Release process refinements](https://gitlab.com/groups/gitlab-org/-/epics/11842) to help users with releasing updates to components in Public Catalog - Your Resources - components that are specific to the user membership - namespace, group, or project. The filtered view can be monetized to ~"GitLab Premium", we should always present the filter, but its content will be available to ~"GitLab Premium" + users only #### Proposed design See the details [in this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/428144/) <details><summary>Milestone 16.6</summary>  - A single index page that shows all components that a user has access to. </details> <details><summary>Milestone 16.7</summary>  A single index page includes a filtered view * Tab filters: `All, your resources` * Filtering options: `name` * Sorting options: `name, released date, created date` </details> #### Future iterations - ~"GitLab Premium" : Filter components on namespace, organization, or release - ~"GitLab Ultimate" : Add "Require org approval for components to be available in catalog" ### Prioritization The issues in each sub-epic are organized as: * ~"Verify::P1" - work that blocks basic feature availability * ~"Verify::P2" - work that introduces important improvements * ~"Verify::P3" - other improvements