Earlier quoted context omitted.
How can I use this code snippet? Apologies if it's obvious to everyone.
On Chrome, I use an extension called 'Stylebot'. Not sure about other platforms.
You can use Stylus on Firefox (and Chrome, too.)
Ask HN: Thoughts on new GitHub layout?
431–440 of 590 posts
Re: Ask HN: Thoughts on new GitHub layout?
#432Earlier quoted context omitted.
Ya, I didn't understand this design choice. For a while I've had some custom css which also extends the width of the main content on github as well because I've always found reading some github issues with logs in them challenging. This is the css I'm running now to fix this, as well as extend the width of the main content. The 1600px is such that when using i3 and having my browser be half the screen it consumes mos…
How can I use this code snippet? Apologies if it's obvious to everyone.
You can use Stylus (https://addons.mozilla.org/en-US/firefox/addon/styl-us/) to add custom CSS to websites.
Re: Ask HN: Thoughts on new GitHub layout?
#433it hurts my soul....why Microsoft? why must everything look like it's a corporate sellout?
Re: Ask HN: Thoughts on new GitHub layout?
#434I'm used to Jira changing their interface more often than my socks get holes in them. So this is small potato and my well trained UX boobytrap avoiding subconscious navigated it beautifully.
Re: Ask HN: Thoughts on new GitHub layout?
#435The design before was targeting developers with a "for work" feel. From a vcs perspective and ci/cd perspective it showed the important stuff. The new file browser is especially bad - being Tritanopia color blind the lack of lines and the folders physically hurt my eyes.
But To be honest we all know what this re-design is for. Microsoft pushing Azure Pipelines ( github actions ). The previous github interface was not cute / nice enough for actions. So they re-designed the entire site to be able to push us towards Azure usage. ( that is the entire reason Microsoft Acquired github - slowly luring developers from opensource to the safe walled garded of microsoft. With a slow shift of Azure cloud offerings leaking in to our minds. ). And slowly taking over most organisations tool-chains.
Re: Ask HN: Thoughts on new GitHub layout?
#436Earlier quoted context omitted.
Reminds me of when HN added the [-] and everybody complained it was on the wrong side but they couldn’t be * to fix it.
I love that it's on the right. It means when on mobile, I don't accidentally upvote something that I meant to collapse.
that's because HN on mobile is bad, not because it's good UI
Re: Ask HN: Thoughts on new GitHub layout?
#437Using inspect, I did two things -
- removed all the rounded edges
- added lines dividing the rows in the files table
Re: Ask HN: Thoughts on new GitHub layout?
#438Earlier quoted context omitted.
That seems like a tradeoff between people discovering a project and people developing that project. People initially discovering a project usually want the README; people developing a project may potentially want either.
I never look at the Code page of projects I work on. I'm always going straight to the pull requests or issues. I always thought the Code page's intended audience was new people checking out the repo for documentation or to peruse the code (usually after checking out the README).
I find that the code helps me get oriented, like running ls in a project's directory after cd-ing to it.
Re: Ask HN: Thoughts on new GitHub layout?
#439>the buttons in the header are separated to the extreme ends of the screen
>...but the elements in the global site header aren't (for some reason)
>the selected tab has a thin underline which is harder to recognize than a colored background, and isn't as clear (does it mean I'm currently hovering over it, does it just mean that section is important, is it the same as a notification badge, etc)
>the main column is off-center
>there's no separation or contrast between the list elements, making it harder to align things by eye
>the readme section doesn't have a header, making it look like the text "README" is part of the document itself
>there's an entire second column in the layout, placing both on an equal level of importance
>...but it only has a single paragraph in it, which leaves you with an empty column taking up space 95% of the time
>if a project doesn't have something, the sidebar will simply omit that section instead of showing the same element with the text "0 releases", "0 branches", etc.
>...which in turn trains you to ignore the contents of that column and not expect to find things there
>this also applies to the "about" text, the purpose of which is literally to be the first thing you see when loading the page - now in the sidebar, sandwiched between three lines of text in the same font, color, weight and length
>the labels at the bottom of the page are spaced out evenly, which actually makes them feel HARDER to click (the sizes of the hitboxes are the same, they're just much further apart) in addition to looking ridiculous
Guys, stop complaining. You're just afraid of change.
Re: Ask HN: Thoughts on new GitHub layout?
#440What do people feel about the code at the top (both old and new)
The thing I think I want at the top is the readme. If I'm looking for repos I need to know what it is before I look at the code. If it's a repo I'm working on I'm more likely to look at the code locally then the code on github. When I do look at the code on github it doesn't need to be on the front page for me. https://github.com/username/reponame/code or the links to various branches would suffice for me. Even if I am looking for the code the 95% of the time the code is not above the fold, instead there are several lines of folders and config I don't care about and so I still have to scroll down or search. In other words, the code at the top doesn't even help for code.
To put it another way, the code at the top is actively hostile to what I need to get done.