-
Notifications
You must be signed in to change notification settings - Fork 360
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
Blockbase: A different approach to navigation #4575
Conversation
I've tested this with Blockbase by adding a menu to the 'social' location. Everything seems to work great - it works at all resolutions and I'm able to edit it via the Menus section and the Customizer. Here's what I'm seeing: Sorry I haven't got any more meaningful feedback... I also didn't see any errors or warnings while testing. |
@kjellr I can't replicate that, but I've added a commit which I hope will address it. How did you get to an "fresh site" state? |
All sorted out now. This works great! The only small thing I noticed is that if you enter an email address/ |
Howdy! This is cool. Nevertheless it feels like a serious workaround, a very specific implementation of this theme's need. I wonder how could the navigation block change to allow one to implement "universal theme blocks-in-menus" easier? There is ongoing effort to change how the navigation block stores its data. It would be lovely if we could chime in with the theme challenges, described in detail, so that the foundational design of the block (which is still evolving) takes them into account as early as possible. |
Closing in favour of #4482 |
Changes proposed in this Pull Request:
In order to add social links to a navigation block (as suggested in #4482) using the Customizer, I believe we need a different approach to navigation. One problem with the current approach is that if a user edits their navigation in the Site Editor, edits can no longer be made in Customizer. Another issue is that our approach to the social menu needs significant rework by the user when they switch to the Site Editor.
This PR proposes a different approach:
The major benefit of this approach is that we can build a navigation block for the Site Editor in any way we want. We can use the nav walker class to convert a PHP nav menu to a block nav menu. It's surprisingly simple!
The only downside with this approach is that if I edit the template via the Site Editor, or the Template editor, and edit it again in the customizer, or menus screen, my previous changes would be overwritten.
To test:
Still to do: