Enhance Navigation admin workflow with Managed Tabs.

while i was testing the new navigation page functionality i had an idea for the "lock in" problem this issue is about. on second thought it is difficult to have a button like "save and go to page x" (the pattern we've ideated in todays meeting - you will never find one single page it would makes sense to go to from here). but since layout builder is used here why not orient towards the pattern used on the manage display page on a content type when layout builder is activated?

when the user gets to /admin/config/user-interface/navigation-block present the help text and a "manage layout" button (the button label is still debatable). at this point the sidebar is still functional. as soon as the "manage layout" button is pressed the page goes into the "layout mode" and the sidebar switches being just a none functional preview. and by pressing the save button in that "layout mode" the user returns to the previous page with the "manage layout" button. that way the user would remain in the context of the navigation block page and the context switch would be also comprehensible and the user wouldn`t be forwarded into a sort of "detached" page where one is being trap in at the moment.

Unifying the two pages into a single page and using local tasks is a good idea, I like that as well, good idea. A few thoughts:

1. I am usually for shorter menu item labels. So i wonder if it would make sense to strike settings and rename navigation settings to navigation. On one hand several menu items in the configuration submenu are using the addition of "settings" but on the other hand the first page / tab within the navigation settings also is called managed settings. plus the prefix "manage" is sort of redundant, for screenreader users, and there are also several issue to remove the verb manage from page/tab titles (for example #2521780: The 'Edit', 'Manage display' and 'Manage form display' tabs were hard to understand #2677102: Word Manage at beginning of multiple admin page names make them hard to distinguish.. So I wonder why not go with Navigationfor the menu items and Settings and Layoutfor the local items. that way all three would be nouns.
2. I still don't like the concept of having two links, one pointing to the frontpage the other to the administration (personally none of the two would be a desired destination i would think of in the context of after adding the navigation block layout). For one having primary buttons for links doesn't feel semantically correct and still it is the same concept like for the database updater. Me as a user dislike ending up somewhere else at the end of a task other than the page i've started at. it still feels like i reached dead end. and the concept of a navigation sidebar and the preview blur on this page. with the suggestion in #11 it would be sort of like a toggle/switch button. the user is deliberately switching between the layout /preview mode and the actual navigation sidebar. one more click upfront but clearer and the user would remain in the context. but maybe there might be also a third option how to tackle this?

Code looks good and the administrative UX has been improved.
Also provides tests.

Thank you!

I just came across this issue and this seems like a big UX change and I need to think a bit about it: the Navigation will handle many more things beyond what we have now (like Top Bar settings), so we need to plan for that before merging pages and hiding them in deeper levels. I'd like to hold big UX changes like this until we all have had time to discuss and agree on them. This needs some time and with DrupalCon planning going on I can't keep up with all issues.

So moving to Needs work not because the code isn't OK, but because we need to discuss the changes :)

In discussion with @mherchel @rkoller & @kat-shaw we decided that this was not a barrier. So not a stable profile blocker, but we should get this fixed.

This is using Layout Builder which is going to be deprecated. Hopefully this gets resolved in the next version.

Revisited this issue to try to improve the the admin workflow.

Could you please indicate the current requirements for this issue? Navigation has evolved since the creation of it and I think some of the points mentioned in the IS have been already addressed.

Made some research about the possible tabs and the creation of the local tasks should not be a big deal.
However, their URLs (/admin/config/user-interface/navigation/settings & /admin/config/user-interface/navigation-block) are not following the generic folder structure. I would suggest to use /admin/config/user-interface/navigation/settings & /admin/config/user-interface/navigation/layout instead. That would lead to broken links in existing sites, and might not be a good idea.

To avoid those broken links we could create a controller that redirects to the new URL as an alternative, and remove it in 13.0.0.

I would suggest to use /admin/config/user-interface/navigation/settings & /admin/config/user-interface/navigation/layout instead. That would lead to broken links in existing sites, and might not be a good idea

This makes sense from my point of view. I think this is mainly a UX improvement.

+1 to get all Navigation related stuff under Navigation and then use tabs.

Sounds good to me.

Created new MR according to last comments, created a Change Record and updated the IS to make it more accurate.

Ready for review.

The Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.