Gutenberg contributors focus their efforts on the navigation block for WordPress 5.9, the navigation editor planned for a future release – WP Tavern
Gutenberg contributors reoriented their efforts to focus on the navigation block prior to WordPress 5.9, leaving the navigation editor for a future release. Recent progress checks have further narrowed the scope of what Matias Ventura previously projected include “both the navigation blocks and navigation screens projects.
“The navigation editor will not be included in WordPress 5.9 because the changes to the block are necessary for the editor to be successful,” Automattic engineer and main contributor Dave Smith noted. “We need to allow enough time to test the editor before any major release and allow for community feedback. “
During a recent Hangout meeting in the hallway, contributors discussed some of the challenges they encountered while working on the navigation editor. Smith said the outcome of this meeting was that “the efforts of the contributors will shift to the Nav block in order to resolve some of the underlying architectural issues.” Contributors and meeting attendees agreed that the navigation editor should be on hold until the navigation block is dispatched.
Smith summarized the updated block-based navigation scope in WordPress 5.9 and the block changes that are needed to move the project forward:
- specifically separate the presentation of the navigation from its data in order to make the navigation reusable. This serves both the Nav Editor project and the WordPress 5.9 version in general.
- The navigation editor will ultimately focus on handling the The data of navigation that is why the above work is a prerequisite for the success of the project.
- Work on the navigation editor will resume after WordPress 5.9. We will continue to focus on backward compatibility while looking to the world of blocks.
- We are unlikely to pursue a new “Classic Menu” block. Instead, focus on the Navigation block (or its data).
As part of the effort to separate presentation from browsing from its data, contributors envision two important public relations that explore different approaches:
Discussion of the pros and cons of both approaches will continue before contributors choose one to move forward. Smith identified the following goals as important factors in the architectural decision:
- Allow navigations to be used in different places in the same model / site.
- Allow the reuse of the same navigation The data but with different presentation treatments.
- Retain the ability to quickly create new navigations.
- Separate presentation and data to allow navigation data to be edited in isolation (for example, the Nav Editor project).
- Allow the reuse of navigation between themes.
While having a full navigation editor is great to kick off with the other full site editing features of WordPress 5.9, it makes sense for contributors to take their time to think about the architectural approach that will define menus in WordPress within. the foreseeable future. Anyone with strong opinions on the future of WordPress browsing should test PR and weigh in on the discussion.