-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v3.0 beta - menu enhancement request #6800
Comments
I'm not a fan of the new side menu either... Those to dropdown menu have a much faster to navigate and don't mess a round with the position you have to click... |
I do like the new menu but I do agree that it does take up a fair bit of space. Perhaps a good solution to this is to make the sidebar collapsible 🤔 |
The tricky part is passing state to the menu, to know which section (if any) should be expanded. We actually did this in much older versions of NetBox to highlight the "active" menu button, but decided it wasn't worth the effort to keep up. I'd like to come up with something a bit more clever than manually specifying the active menu section under each view.
FWIW I ran a very informal Twitter poll where people preferred a sidebar to a top menu roughly 2:1. I imagine it will start to feel more familiar after a bit of use. |
FYI, this is fixed as of 3752cb3. The nav menu is now collapsible and determines the state of the current page and highlights the appropriate menu item accordingly. |
What I don't like about sidebars, is that menu Items get dropped off the screen. Navigation has to be quick without extra clicks to find your way I can understand that the sidebar remains, but that the submenu pops out to the right, as it poped out to the bottom with the top menu. Then the navigation will be more slick Pieter |
NetBox version
3.0
Feature type
New functionality
Proposed functionality
Menu should not close each time you change a view. It makes navigation a bit tedious. For example, when in the
Racks
view (and its subviews), keep theOrganization
section of the menu should stay extended.Use case
Menu in 2.11 has no animations (faster navigation) and the menus groups being horizontally side-by-side makes visually identifying where things are faster - building "visual memory" for where to click to get to a particular view is quite easy due to the static positioning and each element having unique position is easier.
In 3.0, due to animations and everything being in the same vertical menu (with dynamic position due to scroll), it means you consciously have to identify where you want to click, scroll to the position, etc. As most workflows usually happen within a menu group, having it extended when you are in a view inside that menu group would help with that.
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: