<!--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=583019) </details> <!--IssueSummary end--> # Context In the MVC of the file tree browser, the file tree browser was not included in the Project Overview Page per https://gitlab.com/gitlab-org/gitlab/-/issues/19530#note_2432121108. However, the file tree browser is available on the top level directory Repository page. Both pages show the same root directory for the repository, however 1 allows users to see the file tree and one does not. This is inconsistent. <table> <tr> <th>Project overview page</th> <th>Repository top level directory page</th> </tr> <tr> <td> {width="774" height="600"} Directory: `test-project-general` File tree browser: hidden </td> <td> {width="775" height="600"} Directory: `test-project-general` File tree browser: visible </td> </tr> </table> # Research questions 1. Why do users want to see this at the project root? 2. Do external users have the same needs as our internal ones? # Design questions * Is the file tree browser useful on the Repository top level directory page? * What are consistency considerations between the Project overview page \<\> Repository top level directory page? * Should the file tree browser appear on the Project Overview page (information dense, one of the most trafficked pages in GitLab)? * If we did add it to the project root, what's the core difference between the repo file list vs. the repo file tree? * Do we want the file tree to be usable when not in nested folders?