### Update With the new Components and Catalog we are no longer accepting templates as a contribution as mentioned in https://docs.gitlab.com/ee/development/cicd/templates.html and with the new [exit strategy for templates](https://gitlab.com/gitlab-org/gitlab/-/issues/433441 "Define exit strategy for CI templates") we are moving away from templates ### Background Templates provide an easy to get familiar with CI. It could help with CI/CD on-boarding and save time and effort for users when building their pipeline. Vendors take pride in the number of templates they provide to their users. ### Problem to solve New users don't get enough guidance on how to get started with CI/CD. The templates we provide aren't leveraged to their full potential as a tool for CI/CD onboarding. * Templates are not discoverable - the dropdown is context depended * Hard to understand - no explanation, some of the names are internal * Unable to know when a new template is available - we've just introduced a new AWS template, in this current design it's impossible for our users to know that. * Some templates are meant to work as whole pipeline templates, while others are used as "includes", or job templates. We don't differentiate between them in the template dropdown, making it difficult for someone to find, try and leverage the right template. ### Current experience  ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### User experience goal - As a user, I need to easily understand which templates are available for me to use. - As a user, I need to identify new/up-to-date templates. ### Proposal We should design a more efficient way to browse and use the templates that we have. The template names and descriptions should reflect the job the templates help solve. ### Here are several examples from our competitors   ### Visionary mock-up This is an early exploration of one of potential solutions, a dedicated page.  ### Further details While out of scope for the MVC, we should think about how the templates area will help enable our vision for the reusable pipeline and job blocks (see https://gitlab.com/gitlab-org/gitlab/-/issues/280802 )