Started tinkering with a tampermonkey script: https://github.com/mrchief/github-redesign. WIP.
Redesigning GitHub Repository Page
181–190 of 315 posts
Re: Redesigning GitHub Repository Page
#182I don't love the design, but what bothers me more is that I disagree with many of the premises informing the decisions, for example: - Github tab icons are purely decorative - Because we simplified the whole header, we don’t need that color coding anymore - Commits often touch files for completely arbitrary reasons, so the last commit tells you almost nothing - Get rid of gradients, dirty washed-out colors, unnecessa…
> Github tab icons are purely decorative I actually agreed with that one. He made a pretty compelling argument. The icons aren't universal, and I have to read the words every time anyway.
I agree they aren't universal, so it's not so useful for first-time users, but once you get to learn them I find they help a lot with scanning and recognition.
Re: Redesigning GitHub Repository Page
#183Earlier quoted context omitted.
I think the two natures of Github as a tool for software development and Github as a social coding site are often at odds. Some ways this could be reconciled: - greater end user customization of the UI layout - an option to enter a different UI(contributor UI) for repositories you contribute to/own - make the contributor UI an enhancement on top of the current UI(perhaps a new darker tab bar) - related to the above,…
GitHub should go full MySpace, completely custom css per project.
Isn't this github.io ?
Re: Redesigning GitHub Repository Page
#184This is clearly a redesign done by someone who doesn't use GitHub, and doesn't look at anything but the main screen or why it is the way it is - especially when you start digging into the rest of the UI.
The tabs they want to take away from the "code" screen have little or nothing to do with the other main tabs, that's why they're not cluttering up the main nav bar (which doesn't fit into the author's screenshots.
No one cares about the description of the repo if they're trying to interact with the wiki or the issues modes, that's why it's in the code/main section.
Re: Redesigning GitHub Repository Page
#185I don't love the design, but what bothers me more is that I disagree with many of the premises informing the decisions, for example: - Github tab icons are purely decorative - Because we simplified the whole header, we don’t need that color coding anymore - Commits often touch files for completely arbitrary reasons, so the last commit tells you almost nothing - Get rid of gradients, dirty washed-out colors, unnecessa…
> Github tab icons are purely decorative I actually agreed with that one. He made a pretty compelling argument. The icons aren't universal, and I have to read the words every time anyway.
I don't know. In his giant image asking if the icon is the commit icon, my first though was "history".
I was actually looking forward for me being hilariously wrong, and GitHub having made funnily incomprehensible icons, and he did not deliver!
Re: Redesigning GitHub Repository Page
#186[deleted]
Re: Redesigning GitHub Repository Page
#187I don't agree with repository overview. Most people visit home page are not maintainer. They don't care much about commits and statistics.
What they do is reading the README.md or reading code without cloning them to their machine. Perhaps commit message is not important, but the update date reflects how active the repository is.
Re: Redesigning GitHub Repository Page
#188I don't agree with repository overview. Most people visit home page are not maintainer. They don't care much about commits and statistics. What they do is reading the README.md or reading code without cloning them to their machine. Perhaps commit message is not important, but the update date reflects how active the repository is.
To me this sounds like a prime opportunity to have two repo pages: one for contributors/owners, one for everyone else, and the option to toggle the view for each account per repo.
The danger would be overcomplexity/confusion, but if designed to match eachother well with different priorities, it could work. Still, the singular view no matter who you are is certainly a nice feature that may not be worth getting rid of given how universal the repo page design is.
Re: Redesigning GitHub Repository Page
#189There is so much comments about whether the proposal is good or bad. But for me, without making usability tests, there is just no way to know if it's better.
For me proposal for redesign without any experimental data presented is just an invitation to endless speculation.
Re: Redesigning GitHub Repository Page
#190But maybe it’s time to fresh it up a little? Get rid of gradients, dirty washed-out colors, unnecessary separators, add a little more air. No, no, no , NO!!!11 I've had it with these "sea of floating text on an expanse of white" redesigns, seeing yet another one follow this mindless trend just disgusts me thoroughly. The lines, subtle gradients, and other affordances of the old design serve to organise and direct you…
I thought some of his suggestions were pretty decent. But then he just threw everything away by mucking around in the Code, I mean Overview tab. His last design, without the guiding lines, make it look like jumbled shit pie.
I have the same feeling. He proposed a very good changes and then started to mess up Code…