The [Project Sneak Peek exploration](https://docs.google.com/document/d/1FlyCqdyRvvHjISP8QWxP_UD-derCrzE9BC1uHIPHtjk/edit?tab=t.0) highlights the absence of defined templates as a major source of inconsistency and inefficiency across the product experience. This causes redundant decision-making by teams, fragmented layouts, and a high cognitive load for users navigating between pages. Establishing a core set of reusable, consistent layout templates and patterns will help align the product and enable the rollout of a modernized design direction. In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/3148+ we explored which layouts we want to move forward with as our starting point: * Application chrome * [Panel](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/work_items/3186) (base component) * [Index](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/work_items/3187) (page composition) * [Detail](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/work_items/3188) with right sidebar (page composition) Currently, we have a mix of how the Panel header is used. In the static panel, we always display the page breadcrumb, while in the dynamic panel we show a page identifier, and in the AI panel, we show Duo's feature title.
 We want to make more consistent structural use of Panels within the Application Chrome. This effort aims to unify how we use the Panel header (via templates) and moves the Breadcrumb onto the global surface of the Application Chrome. Templates begin at the Panel level and include built-in Panel actions, with page-level actions, a Panel identifier, and a Page heading. We start with two simple layouts wich are commonly used across the product today: - [Index](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/work_items/3187) - [Detail](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/work_items/3188) <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> > [!important] > This page may contain information related to upcoming products, features and functionality. > It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. > Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->