4 ms·
Now I'm wondering if I'm alone in saying that this completely goes against my experience with Github. The layout at the top of the page is roughly hierarchical
by Groxx 15y ago
Now I'm wondering if I'm alone in saying that this completely goes against my experience with Github.
The layout at the top of the page is roughly hierarchical with a header for your account (which is standard). You have (edit: my numbers do not match the ones in the article):
1. where you are (project)
2. what you want to see (code, issues, etc) (within that project)
3. branches, commits, etc (associated with the code in the project)
4. latest commit (to the code in the branch in the project)
5. code
There's a clear progression from "project" to "code", with only minor hiccups along the way (the description has to do with the whole project, but then it's pointless to have it at the top of every page, so it's beneath a single tab). And the latest commit seems arbitrary, IMO - it doesn't convey much useful information, aside from the 'freshness' of the project.
On the issues page, the 'new' button is next to the search field because they want you to search first. If you look for a search bar (standard in the top-right corner), because you should be doing so anyway rather than duplicating reports, you would find the new issue button immediately. This is relatively standard UI for a publicly-accessible bug-report-like system.
There are rough parts of Github's UI, definitely. After seeing a mention that it was hard to find how to change to an organization, I tried - very strange and non-obvious that it's only on the root page (that I've seen). And the different layouts between the main tabs for a project could be a lot more consistent. And commits could use a --graph display.
But the main project page? I've always found that to be the single least confusing part of the entire site, and the most immediately-useful. I've used nearly every control on the page multiple times, and hiding them behind more layers of access would only impede normal use of the site.
- hellerbarde 15y agoI agree with you, I like the main project page a lot as well. One improvement could be to either fade out (and fade in on mouseover) or darken the 3,4,5 block (numbers from the link). This would have the effect of either hiding the block so you could be drawn to the menus below (where the real info lies), or to make it stick out more, so your eyes could use it as a point of reference. right now it all kind of melds together.
- knewter 15y ago> it doesn't convey much useful information, aside from the 'freshness' of the project. But that's one of the most useful bits of information imo. When I'm reviewing projects to see which I will use, that is one of the two most important determining factors (the other being tests, all other things being equal)
- Groxx 15y agoThere is that, yeah. But that's a lot of screen real-estate for viewing the last-updated-at date for a project, and it's in a different color than other things on the page so it draws your eye. Probably intentionally for this reason. Do you mostly value the commit's date, or any of the other information in that block? I've only ever cared about the date, personally.
- roryokane 15y agoI think they show the latest commit to match Git's model where each commit has its own file tree. If you are looking at an old version of the code, the latest commit for that version uniquely identifies that version. I suppose they show the latest commit as part of a way to prevent people from getting confused which version of the code they are looking at, when they look at past versions of the files. But I think in the case of the project main page, the latest commit is too rarely used to justify being shown by default. I think GitHub should only show the full latest commit when browsing past versions of code. Otherwise, it should show just the text "latest commit for the master branch", or that commit's SHA ID, or the date of the last update. If allowing people to measure project "freshness" is important enough, maybe they should instead show the 52-week graph of recent activity, like on users' project lists.