ianstewart
commented
3 years ago ...or how can we let people manage menus from within the block editor? How can we make that connection to the Customizer more obvious? How do we make the connection between Pages and menus clearer?
This part will not be a size small. :)
Definitely on the core roadmap. Definitely the plan, as I understand it, for the Gutenberg plugin to use Navigation Block derived menus as a default. There'll be a block-based screen for editing menus in June, I believe. And I think core might work on translating menus from the customizer to the block. Not sure on the last part there.
That all said, I think we might be doing something silly here on Dotcom. :)
That's a brand new site that has no pages. But it has a menu set up.
Two things jump out.
- In the now column: @simison can we make sure that menus are not created when there are no pages?
- In the future column: When we create headers in our FSE flow we should consider just making a menu for them as well so they don't have to select.
The Navigation menu blocks offer several options, the most prominent is using an existing menu:
But for a brand new site, there's no reference to where that "Primary" menu came from, or how to change it. And in this case, the only menu item in the primary menu is a link to the home page; not really much of a "menu". :)
As an "insider", I know that I need to set up my menus in the Customizer before I can select them in the block editor. Creating a menu that can be reused and updated in one place is one of the things that makes the menu block powerful and useful.