{"id":22,"date":"2024-06-21T02:34:14","date_gmt":"2024-06-21T02:34:14","guid":{"rendered":"https:\/\/think-twice.me\/?p=22"},"modified":"2024-06-21T02:34:14","modified_gmt":"2024-06-21T02:34:14","slug":"a-different-github-design","status":"publish","type":"post","link":"https:\/\/think-twice.me\/?p=22","title":{"rendered":"A different github design"},"content":{"rendered":"\n

Earlier today HN reviewed a proposed github redesign<\/a> and largely didn\u2019t favor it.<\/p>\n\n\n\n

I figured I\u2019d take a stab at it<\/p>\n\n\n\n

Before:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

After:
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

See the proposed before-and-after pictures above.
Here are some principles that seem intuitive to me, and maybe designers might consider them too.<\/p>\n\n\n\n

    \n
  1. The visibility of an item should be proportional to its usefulness. This includes size, placement, brightness\/colorfulness.<\/li>\n\n\n\n
  2. There is always<\/strong> a flexible solution which caters to both experts and novices simultaneously.<\/li>\n\n\n\n
  3. Hierarchy of UI should reflect conceptual hierarchy.<\/li>\n<\/ol>\n\n\n\n

    In practice here are the things I changed in my mockup, based on those 3 rules:<\/p>\n\n\n\n

      \n
    • Create new file has no business being on the same line as \u201cClone repo.\u201d It is a branch-specific operation next to a repo-specific operation.<\/li>\n\n\n\n
    • The current-branch dropdown\/button should connected-to the file-list widget. The file-list widget is showing files of that branch<\/em>. The two are logically interdependent but visually separated.<\/li>\n\n\n\n
    • Wiki and Insights are features I have never used on github and may never use. They should be hidden by default. They can intelligently show for repos that have ever once used those features.<\/li>\n\n\n\n
    • The repo description shouldn\u2019t be in the code tab. The repo description is an attribute to the repo itself<\/li>\n<\/ul>\n\n\n\n


      Good luck on your design journeys.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Earlier today HN reviewed a proposed github redesign and largely didn\u2019t favor it. I figured I\u2019d take a stab at it Before: After: See the proposed before-and-after pictures above.Here are some principles that seem intuitive to me, and maybe designers might consider them too. In practice here are the things I changed in my mockup,…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-22","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/think-twice.me\/index.php?rest_route=\/wp\/v2\/posts\/22","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/think-twice.me\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/think-twice.me\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/think-twice.me\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/think-twice.me\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=22"}],"version-history":[{"count":1,"href":"https:\/\/think-twice.me\/index.php?rest_route=\/wp\/v2\/posts\/22\/revisions"}],"predecessor-version":[{"id":26,"href":"https:\/\/think-twice.me\/index.php?rest_route=\/wp\/v2\/posts\/22\/revisions\/26"}],"wp:attachment":[{"href":"https:\/\/think-twice.me\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=22"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/think-twice.me\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=22"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/think-twice.me\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=22"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}