<!--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=585815) </details> <!--IssueSummary end--> ## Proposal Update the Code dropdown to organize and group the multiple options in the Code menu 1. Eliminates that row of many buttons for download format. - Related to https://gitlab.com/gitlab-org/gitlab/-/work_items/432363+ 1. Simplifies the SSH/HTTPS grouping of actions temp [Figma file](https://www.figma.com/design/ej9FR4BxOsEqtUdc7rOIJp/MLE-ideas---concepts?node-id=791-12149&t=N1WTygeOvYL5DaKr-1) | Current | Proposal | | ------ | ------ | | {width=423 height=600} | {width=423 height=600} | ## Considerations - `@mle` had concerns about adding tabs in the past to disclosures and some recent thoughts on this from [Slack](https://gitlab.slack.com/archives/CLW71KM96/p1767762787294669) - `@trevorpierce` tabs within a disclosure should be avoided for the cognitive load they can add. If I'm opening a disclosure, I'm already keeping the clicked item name in memory, so the choices presented have some context. If we add tabs as a way to show and hide different facets of that context, we're doubling or tripling the pieces of information the user has to remember just to make an informed click. This cognitive load stacking increases significantly for screen reader and voice command users. - (in context of vertical tabs) `@jeldergl` I don't consider tabs to be navigation. They're content-switching rather than wayfinding. Changing the view rather than selecting the destination. - `@alyssatrinh` Idea: What if we condensed the "Open with" into a dropdown, like you did for the Download options?