<!--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=520774) </details> <!--IssueSummary end--> ### Problem In **Settings → Repository → Repository Maintenance**, there is a **danger_alert** informing users that they should export their project before performing destructive actions. The alert includes a link to the **Importing and Exporting Projects** documentation page. However, in the documentation, we direct users to **Settings → General → Advanced** to export their project. This creates an unnecessary detour: 1. Users follow the **danger_alert** link to the documentation. 2. The documentation redirects them to **Settings → General → Advanced**. 3. Once there, users can proceed with exporting their project. Additionally, in **Settings → General → Advanced**, the **Export Project** section also contains the same link to the **Importing and Exporting Projects** documentation. This means users see the same documentation link **in both locations**, making the extra redirection redundant and potentially confusing. ### Proposal Instead of linking to the documentation, the **danger_alert** in **Settings → Repository → Repository Maintenance** should **directly link users to the Export Project section in Settings → General → Advanced** (`/settings/general/advanced`). This would streamline the workflow by removing an unnecessary step. ### Current Flow vs. Proposed Flow #### Current Flow ```mermaid graph TD; A[User in Repository Maintenance] -->|Clicks alert link| B[Docs: Importing and Exporting Projects]; B -->|Reads instructions| C[Navigates to Settings → General → Advanced]; C --> D[Exports Project] ``` #### Proposed Flow ```mermaid graph TD; A[User in Repository Maintenance] -->|Clicks alert link| B[Settings → General → Advanced]; B --> C[Exports Project] ``` ### Benefits - **Reduces friction**: Users no longer need to read the documentation just to navigate to the correct settings page. - **Eliminates redundancy**: The documentation link appears in both locations, making it unnecessary in **Repository Maintenance**. - **Increases efficiency**: Direct navigation saves time and cognitive load. - **Aligns with existing UX patterns**: The **Export Project** section already has the relevant link, making the extra documentation step redundant. ### Next Steps - Update the **danger_alert** in **Settings → Repository → Repository Maintenance** to link directly to `/settings/general/advanced`. - Ensure proper permissions and contextual messaging remain intact. Would love feedback from UX/Product on whether any edge cases should be considered!