<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=550136) </details> <!--IssueSummary end--> # Context There are several areas of GitLab that use tree navigation in addition to traditional navigation as a list. Tree navigation allows users to maintain context while navigating nested directories with several layers. It is standard in code development tools. However, tree navigation elements currently appear differently across 3 different GitLab products. While we should prioritize what's best for users in specific workflows, there may be an opportunity to unify the designs a bit more for design system consistency. <table> <tr> <th> Source Code \> Repository </th> <th> Merge request \> Changes tab </th> <th>Security Inventory</th> </tr> <tr> <td> {width=268 height=190} {width=771 height=546} Currently in development https://gitlab.com/groups/gitlab-org/-/epics/17781 </td> <td> {width="994" height="824"} [Example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/193200/diffs) </td> <td> {width=1186 height=782} [Example](https://gitlab.com/groups/gitlab-org/-/security/inventory) </td> </tr> </table> # Design proposal ### **_TBD_**