FSE Navigation Block Woes  ## Metadata - Author: [[Brian Coords]] - Full Title: FSE Navigation Block Woes - Category: #articles - Document Note: --- tags: - BlockEditor - WordPressNavigationBlock - GutenbergDevelopment Author: [Contributor to WordPress Block Editor] Source: [GitHub/WordPress Forum] Reference: [GitHub Issue Link](https://github.com/WordPress/gutenberg/issues/new) date created: 2024-09-10 14:35 --- # Title: Navigation Block Development Updates and Contributor Insights ## Table of Contents: - [Summary](#summary) - [Main Content](#main-content) - [Navigation Block and Classic Menus](#navigation-block-and-classic-menus) - [Menu Location and Conversion](#menu-location-and-conversion) - [Slug-Based Menu Reference](#slug-based-menu-reference) - [Contributor Feedback](#contributor-feedback) - [Notes](#notes) - [References](#references) - [Paraphrase](#paraphrase) - [Newsletter](#newsletter) - [Action Items](#action-items) - [Hypotheses](#hypotheses) - [Methodology](#methodology) - [Questions](#questions) - [Future Research](#future-research) - [Implications](#implications) - [Logical Validity](#logical-validity) - [Conclusion](#conclusion) ### References: - [GitHub PR Discussion on Navigation Block Enhancements](https://github.com/WordPress/gutenberg/pull/42809) ## 📝 Summary: The contributor explains several key aspects of the WordPress Navigation Block's limitations, particularly with compatibility between the new block-based system and the classic menus. They acknowledge community frustrations, address the lack of backward compatibility, and describe ongoing efforts to improve the Navigation Block, such as transitioning from unique IDs to slugs for menu references. The contributor invites further collaboration via GitHub. ## 📖 Main Content: ### Navigation Block and Classic Menus The core Navigation Block cannot operate alongside the classic Menus interface. Contributors intentionally chose this design, as providing backward compatibility for the Classic Menu screen was not feasible due to the extent of changes and enhancements introduced in the block editor. ### Menu Location and Conversion When a menu is pulled into the block editor, it converts and the concept of “location” from the classic theme does not transfer meaningfully. This is because block themes do not rely on predefined menu locations. Contributors are open to suggestions on how the editor could handle expectations regarding inferred menu locations. ### Slug-Based Menu Reference Contributors are working to implement slug-based references for menus to provide a more site-agnostic way of managing menus without depending on site-specific IDs. While this issue has been acknowledged for some time, the transition to slugs remains a work in progress. ### Contributor Feedback The contributor stresses the importance of community input, whether through testing, raising issues, or submitting pull requests. They acknowledge ongoing frustrations and highlight that while the block has improved in recent releases, there is still much work to be done. ## 🗒️ Notes: - The Navigation Block is incompatible with the classic Menus system, and backward compatibility is not feasible. - No meaningful transfer of "menu location" from classic themes to block themes. - Work is in progress to switch to slug-based menu references. - Contributors are open to community feedback through GitHub and WP Slack. ## 📖 References: - [GitHub Issue Discussion on Navigation Block](https://github.com/WordPress/gutenberg/issues/new) - [Navigation Block PR on Slug-Based Menus](https://github.com/WordPress/gutenberg/pull/42809) ## 🗣️ Paraphrase: 1. **Original**: "You cannot use the core Navigation block and still be controlling the menu through the classic Menus interface." **Paraphrased**: "The Navigation Block and the classic Menus interface are incompatible, as managing menus via the classic system does not apply within the block-based framework." 2. **Original**: "We are looking to move to slugs to ‘reference’ menus but this is still in the works." **Paraphrased**: "Plans are underway to transition menu references to slugs, but the solution is still under development." ## 📰 Newsletter: 🎉 **WordPress Navigation Block Enhancements: Contributor Insights** If you're working with the WordPress block editor, you'll want to stay updated on changes to the Navigation Block. Contributors are working hard on improving the way menus are managed in block-based themes. There's a shift underway to implement slug-based references for better menu management, replacing the older site-specific IDs. The WordPress community is encouraged to test, report, and collaborate on GitHub to continue enhancing this essential feature. Want to get involved? Check out the GitHub issue thread here: [GitHub Navigation Block](https://github.com/WordPress/gutenberg/issues/new). ## ✅ Action Items: - Investigate transitioning from ID-based menu references to slug-based references in the Navigation Block. - Participate in testing new features for the Navigation Block and raise issues for improvement. - Follow discussions on menu location handling in block themes to contribute feedback on potential solutions. - Engage in GitHub discussions or submit PRs related to the ongoing Navigation Block improvements. ## 🧪 Hypotheses: - **Hypothesis 1**: Moving to slug-based references for menus will increase flexibility in menu management across WordPress sites. - **Hypothesis 2**: User adoption of the Navigation Block will improve once more site-agnostic referencing (slugs) is implemented. ### 📊 Methodology: - **Data Collection**: Track the number of issues raised and closed related to Navigation Block updates. - **Design**: Monitor community feedback pre- and post-implementation of slug-based references for menus. - **Analysis**: Compare usability metrics and community adoption rates for the Navigation Block before and after the updates. ### ❓ Questions: - What challenges do users face when transitioning from classic Menus to the Navigation Block? - How can the block editor better handle inferred menu locations for improved usability? ### 🔮 Future Research: - Investigate the impact of slug-based references on multisite installations and other complex WordPress setups. - Explore user feedback on other pain points in managing menus within block themes. ### 💡 Implications: The shift to slug-based references could make menu management more efficient and adaptable across various site setups. However, addressing user expectations regarding menu location and handling legacy systems remains critical for the block editor’s ongoing success. ### ✅ Logical Validity: - **Causal Reasoning**: The argument for moving to slug-based references is sound, as it directly addresses issues with menu management across different site structures. - **Balanced View**: The contributor acknowledges existing frustrations while also emphasizing ongoing efforts to improve the Navigation Block, showing a balanced understanding of both limitations and progress. ## 🎯 Conclusion: The WordPress Navigation Block represents a significant step forward in site design, but compatibility issues with classic Menus and challenges around menu location transfer remain. Ongoing work, including the shift to slug-based references, aims to make the Navigation Block more flexible and user-friendly. Contributor engagement and community feedback are essential in shaping these updates and driving future improvements. - Document Tags: [[wordpress]] [[full site editing]] - Summary: The document addresses concerns about the navigation block in the WordPress block editor and highlights that using the core Navigation block does not allow control of the menu through the classic Menus interface due to intentional design decisions. It explains that once a menu is pulled into the navigation block, it's converted without the location being saved or applied in a meaningful way in block themes. The document acknowledges known issues and ongoing efforts to improve the system by moving to slugs to reference menus, inviting user feedback and contributions to continue enhancing the block editor's functionality. - URL: https://www.briancoords.com/fse-navigation-block-woes/ Hi Brian, Long time contributor to the block editor (and specifically the Nav block) here. I’ll try and answer a few of your questions, although I am just one of the many contributors. > You cannot use the core Navigation block and still be controlling the menu through the classic Menus interface. That is correct. This was an intentional design decision as providing backwards compatibility for the whole spectrum of enhancements to the Classic Menu screen was not seen as achievable. You are encouraged to manage menus in your block theme via the new block-based system. > Once you pull a menu into the navigation block it will be converted and the menu location is not saved/applied in any meaningful way. That’s correct. There is no concept of “location” in block themes and so we have not been able to meaningfully bring this across and apply it from a classic theme setting. Perhaps you would expect the editor to infer a suitable location (e.g. header template part) within the site based on the “location” attribute? I’d love to understand more your expectations here (a good forum is an Issue on the Github repo <https://github.com/WordPress/gutenberg/issues/new/>). > …which was a more site-agnostic way to keep a reference to a specific menu without relying on site-specific unique IDs This is a known issue and one we’ve been trying to get around to solving for some time. TL;DR – we are looking to move to slugs to “reference” menus but this is still in the works. Please see <https://github.com/WordPress/gutenberg/pull/42809>. In short, I understand all these frustrations and contributors are indeed aware of many of them. We’d love your input, whether that’s in the form of testing, raising Issues or even submitting PRs. The block has improved in recent releases, but – as evidenced by your frustrations here – there’s still lots to do. I just wanted to reach out to say “we hear you”. Thanks again for posting this and I hope to engage with you on Github, WP Slack in the near future., FSE Navigation Block Woes, Brian Coords, 01hq63bb2m4fwzj0kza4m6612n.