{
  "id": 20411338,
  "title": "Github Redesign",
  "url": "https://urgent.news/2026/11/17/github-redesign",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-17T09:28:18.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://tonsky.me/blog/github-redesign/"
  },
  "original_language": "en",
  "account": "GitHub's design is functional and clean, offering a consistent visual language suitable for daily use. However, there are several areas for improvement. To begin with, let's examine the repository page interface and identify the issues it presents.\n\nOne of the primary concerns is the information architecture, particularly the presence of nested tabs. These tabs are nested under one another, making them difficult for non-programmers to grasp, remember, and navigate. Additionally, the grouping of these tabs is often non-intuitive. Nested tabs are considered one of the worst UI patterns due to their complexity.\n\nAnother usability issue arises when users need to access releases within a repository. There is no explicit \"Releases\" tab visible, forcing users to deduce that releases are part of the codebase. This is illogical, as releases are as relevant to the code as issues or wikis.\n\nTo address these issues, we can flatten all tabs into a single navigational control, making them more accessible from anywhere within the repository. This change not only improves accessibility but also frees up valuable vertical space. A larger space allows users to view more content and reach it quickly.\n\nHowever, there remains a challenge with the positioning of the tabs. To resolve this, we can remove the icons and reposition the Settings tab above the tabs. This adjustment ensures that the settings area belongs to the entire repository rather than just the code.\n\nRegarding the icons, they serve as visual cues to help users quickly scan the UI. However, they are often poorly implemented. For example, repository-related icons are abstract and lack understanding, making them ineffective. GitHub has recognized this and dimmed the icons, acknowledging that users will read the labels anyway.\n\nIn addition to these changes, we can enhance the appearance of certain elements. For instance, moving the \"Watchers\" metric to the left side of the page increases its visibility and prominence. Furthermore, modifying the checkmark icon in the \"Watch\" button to be more conspicuous improves its readability.\n\nOverall, these refinements aim to improve the usability and clarity of GitHub's interface, ensuring that users can navigate and interact with the platform more efficiently.",
  "summary": "I suggest the conversation steer away from the controversial last point where he flattens the UI quite a bit to make it less \"dated\", as the rest was quite good up until that point, and that deserves being discussed. Comments",
  "key_points": [
    "GitHub's design is functional but has usability issues",
    "Nested tabs make navigation difficult for non-programmers",
    "Flattening tabs improves accessibility and frees vertical space"
  ],
  "editors_take": "Flattening the navigation and clarifying icon usage transforms the repository interface from a complex hierarchy into a more accessible workspace that prioritizes efficient content discovery for all users.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}