Live data from Hacker News

Redesigning GitLab's navigation

about.gitlab.com

31–40 of 85 posts

Re: Redesigning GitLab's navigation

#31
Hope, the design would be good. The issue I have faced so far is that the navigation (and several other features of GitLab site) doesn't work well when javascript is turned off. The equivalent features in Github works without javascript with no much issues.

Hope this will be fixed.

Re: Redesigning GitLab's navigation

#33
post #30

Is it really accepted best practice for UX testing to use a sample size of 12? That sounds remarkably low to draw product conclusions.

It's qualitative research: as long as you take sufficient precaution picking the subjects to avoid obvious blind spots, it should be enough to get a rough idea of glaring mistakes or problems and to get a good feel of how users perceive and navigate the UI. It also allows you to individually observe effects that would often be "averaged out" by a larger sample. It's being used as a first step (before they conduct a broader quantitative research) so it sounds pretty valid.

Re: Redesigning GitLab's navigation

#35
post #2

You can tell someone is copying someone else's work when they copy the bad stuff. The search box on GitHub and now GitLab wastes space with "This repository" spelled out. It's also odd that you get more space to type when you're not searching inside of a repo, and that backspace is how you switch to a more general search. Pity. I thought that GitLab had learned their lesson and stopped copying GitHub. Aside from that…

>You can tell someone is copying someone else's work when they copy the bad stuff. Once people learn a UI, they really hate deviations from it. It doesn't matter whether githubs UI is good, and it doesn't matter whether gitlab's UI is better. People are used to github, and the peanut gallery will bitch if things are different. The trick for gitlab will be in finding the UI differences that give the maximum improvemen…

> Once people learn a UI, they really hate deviations from it. It doesn't matter whether githubs UI is good, and it doesn't matter whether gitlab's UI is better. People are used to github

This used to be called the "do it like Amazon" rule, which was valid until about 2004-2005 or so.

Re: Redesigning GitLab's navigation

#37

I really like the UI paradigm built by gitbucket - https://gitbucket.github.io/ . Its like they took Bitbucket and made it better. On that note - I cant believe how unusable Bitbucket is. P.S. And obviously love the fact that it is a single jar file deploy.

When did you last try Bitbucket? Bitbucket Cloud or Bitbucket Server (on-prem)?

I write add-ons for Bitbucket Server. I'm curious to know what you find unusable about it.

Re: Redesigning GitLab's navigation

#39
post #9

Something I found missing is the missing shortcut to easily go the page of "merged request assigned to me" (which is the link 'merge request' in the global menu) as it's the single page I visit the most every day at work, to see across all projects , the merge requests that i need to check.

The third icon from the right is a quick link to "Merge Requests Assigned to Me" and it is the same as in the old version of the menu. The quick link in the hamburger menu was simply a duplicate place to find this action. To see all "Merge Requests" in a project, you will find that option in the sidebar now, as that is contextual to the Project you are in.

Sorry , I meant "keyboard shortcurt" , I know the link on the left menu is to go to this page, but at least in 9.2, if you have a long page, you need to scroll up to the reach the top, which is inefficient, and for which a keyboard shortcut would be extremely welcome. There's already one, but for only the merge request of the current project.

Re: Redesigning GitLab's navigation

#40

My first thought on seeing this headline was "what, again?" Don't get me wrong, the new design looks great, but it feels like every six months they switch between having side navigation and putting everything on top. Every time they change there's a definite improvement, but you'd think they'd be able to come up with a design that works for at least a few years.

This happened with GitHub too, IIRC.
Post reply on HN