Title: Hallway Hangout Summary: “compare and contrast” the Navigation screens Author: David Smith Published: August 25, 2021 --- [ ](https://profiles.wordpress.org/get_dave/) [David Smith](https://profiles.wordpress.org/get_dave/) 10:01 am _on_ August 25, 2021 Tags: [feature-navigation-block-editor ( 4 )](https://make.wordpress.org/core/tag/feature-navigation-block-editor/), [hallwayhangout ( 15 )](https://make.wordpress.org/core/tag/hallwayhangout/), [navigation ( 4 )](https://make.wordpress.org/core/tag/navigation/), [summary ( 980 )](https://make.wordpress.org/core/tag/summary/), [video ( 6 )](https://make.wordpress.org/core/tag/video/) # Hallway Hangout Summary: “compare and contrast” the Navigation screens This post summarises the Navigation screen Hallway Hangout held on [2021-08-24 09:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210824T0900) in Zoom facilitated by [@get_dave](https://profiles.wordpress.org/get_dave/), [@talldanwp](https://profiles.wordpress.org/talldanwp/) and [@javier](https://profiles.wordpress.org/javier/). The blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.- based Navigation editor screen has been behind an [“experimental” feature flag](https://github.com/WordPress/gutenberg/blob/571588dc119725e708bd93cbb71b2a161b51a003/lib/init.php#L49-L60) within the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. for some time. The purpose of the call was to **outline the work required in order to remove the “experimental” status from the screen** in order that the editor is **active by default in the Gutenberg _plugin_**. The team working on the feature feel this is valuable in order to increase the visibility of the feature and therefore improve the quantity of feedback we receive. ## Meeting Recording If you’d like to watch the full recording of the session you can do so below: ## Key points agreed It was agreed that the prerequisite for removing “experimental” was: **_UIUI User interface/UXUX User experience_ feature parity with the existing Navigation screen(` nav-menus.php`) in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..** We also acknowledged that: * We wouldn’t commit to feature parity of _developer_ focused APIs at this stage. * Removing “experimental” in the Gutenberg _plugin_, would not automatically make the feature ready for merging into Core (that won’t happen until WordPress 5.9 _at the earliest_). ## What was discussed? The format of the hangout was an open discussion comparing and contrasting the classic menu screen with the experimental block-based navigation screen. To this end attendees were asked to test drive both screens and note down their findings prior to the call. The meeting facilitators also prepared [a list of items](https://docs.google.com/spreadsheets/d/1UB6fMaPmQPGr-xf_R0-P3Mjef_Fhe7UJOBc0dir1GjA/edit#gid=0) as discussion points which were worked through during the call. Each item was demonstrated, discussed and then assigned a loose priority of High/ Medium/Low based on how critical the group felt the issue was to achieving feature parity. ## Outcomes The key outcomes of the call were: * A clearer understanding of the current project roadmap and the next steps required. * A [list of items where the block-based Navigation Editor does not have UI/UX feature parity with the existing Navigation screen](https://docs.google.com/spreadsheets/d/1UB6fMaPmQPGr-xf_R0-P3Mjef_Fhe7UJOBc0dir1GjA/edit#gid=0). * A rough hierarchy of task priorities from which to reprioritise [the Navigation Editor tracking issue](https://github.com/WordPress/gutenberg/issues/29102). ## Next Steps Contributors working on the Nav Editor will now look to reorganise and reprioritse the tracking issue around the problems identified during the call. * All items will be added to the tracking issue (with the possible exception of bugs). * The `High` priority section of the tracking issue will be reformed and refocused around the goal of “removing the experimental status from the Navigation Editor”. Only tasks _directly_ related to this goal will be considered for inclusion in the “High” priority section. * Tasks identified during the call that were marked as `Medium` or `High` till be added to the aforementioned `High` priority section of the tracking issue. * Contributors will focus on tackling `High` priority tasks in order to realise the goal of removing the “experimental” status. All contributors are encouraged to become involved in prioritisation. Everyone is welcome and we’d very much value your feedback. If you feel a priority is wrong or missing then please let your fellow contributors know. Thanks to everyone who attended the hangout and we look forward to moving the Navigation Editor forward together. [#feature-navigation-block-editor](https://make.wordpress.org/core/tag/feature-navigation-block-editor/), [#hallwayhangout](https://make.wordpress.org/core/tag/hallwayhangout/), [#navigation](https://make.wordpress.org/core/tag/navigation/), [#summary](https://make.wordpress.org/core/tag/summary/), [#video](https://make.wordpress.org/core/tag/video/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2021/08/25/hallway-hangout-summary-compare-and-contrast-the-navigation-screens/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2021/08/25/hallway-hangout-summary-compare-and-contrast-the-navigation-screens/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2021/08/25/hallway-hangout-summary-compare-and-contrast-the-navigation-screens/?share=bluesky) * [ X ](https://make.wordpress.org/core/2021/08/25/hallway-hangout-summary-compare-and-contrast-the-navigation-screens/?share=x) * [ Facebook ](https://make.wordpress.org/core/2021/08/25/hallway-hangout-summary-compare-and-contrast-the-navigation-screens/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2021/08/25/hallway-hangout-summary-compare-and-contrast-the-navigation-screens/?share=linkedin) # Post navigation [← WordPress 5.8.x release team and 5.8.1 schedule](https://make.wordpress.org/core/2021/08/24/wordpress-5-8-x-release-team-and-5-8-1-schedule/) [Dev chat summary, August 25, 2021 →](https://make.wordpress.org/core/2021/08/26/dev-chat-summary-august-25-2021/)