-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Navigation on Browse Mode: Make navigations in the list selectable. #50579
Comments
Now that this sidebar is a drill down sidebar can we avoid horizontal scroll bars caused by expanding deeply nested trees by navigating navigation menus using drill down as well @jasmussen ? |
As a hub for both light-weight editing and content access, the drilldowns are a way to pick an individualpage to see just that, then edit or configure it if you like. For just a simple menu of pages, I like to think that we'd avoid deep nesting. As discussed, only simple menus should be editable right there on the left. Any menu that is "complex" (a heuristic we can work out together) you only see the name of the menu, but you edit the menu in the fullscreen editor. We can simply decide that menus with dropdowns are "complex". What do you think? |
We can definitely try this. It depends on how well we manage to achieve the edit in isolation thing. If that turns our great, yes this could be a way. But I suspect people will want to add submenus in an initially simple menu. If I have
and then I want pages for each service and a service is made of sub items, I may want to do it right there:
if we decide "menus with submenus are complex", then if the user has a simple menu open in the sidebar and they use the Plus to add, should they also be allowed to add nested items directly or do we do that in detail view alone? |
If editing on the left works well enough for 1 level submenus, seems fine. |
This is ✅ |
What problem does this address?
Following on from #50578, each of the navigations in the list should be selectable.
When users select a navigation from the list, update the navigation list view in the global sidebar to show the selected navigation, and show only that navigation menu in the preview. Also update the URL so that each navigation has its own direct URL and users can navigate the UI with URL history. This is unnecessary in the case where users have only one navigation.
The text was updated successfully, but these errors were encountered: