Repository navigation
Description
What
This issue tracks a set of proposed improvements to editing Navigation Menus in the Site Editor, targeting WordPress 7.3.
Each idea comes from Create not Learn, an exploration from Automattic of how to make the Site Editor more approachable, so people can build their site without first having to learn how WordPress works. Each one has a working prototype.
🎥 For context, watch the Navigation Menus section of my prototype walkthrough video, from 17:05.
🧪 Try it yourself in the working demo in WordPress Playground. The demo code lives in #86188.
🔌 These flows are now in the Create Not Learn editor plugin, where you can try them together in WordPress Playground. There's also a newer walkthrough of menu editing, from 17:58.
This builds on the 7.2 work in #77069, which completes the list view editing experience in the Site Editor Navigation sidebar.
Why
Navigation Menus are one of the most persistent sources of confusion in the Site Editor. The default menu is a single Page List block that people have to understand before they can change it, people can't find how to add anything other than a Page, building a dropdown is fiddly, adding items one at a time is slow, and editing a menu gives no sign of where else it appears.
Each sub-issue tackles one of those problems directly.
How
None of these ideas should ship in WordPress until they've been tested with real users.
The prototypes show one person's take on each problem. They're a strong starting point, but we need evidence that they work for the people we're building for before they land in Core.
Every item in this issue should follow the same workflow:
- Prototype at low fidelity. Build the smallest thing that lets people try the idea. Skip polish, edge-case handling and tests at this stage, so we can change direction cheaply.
- Run user tests. Put the prototype in front of users to find edge cases and weak points, and to check the idea fits how people actually think about their menus.
- Iterate and refine. Update the prototype based on what testing shows, then test again. Repeat until user tests are consistently reporting good feedback.
- Bring the code to production quality. Only once the design is validated, rebuild or harden the code to Core standards and add tests.
Each item can move through this workflow on its own, and ship as its own PR once it reaches step 4. Findings from testing should be posted back on the relevant sub-issue, so the reasoning behind each decision stays visible.
I'm keen to hear what others think, especially from anyone who has run user tests on Navigation before.
Foundational work
Alongside the user-facing ideas, three long-standing issues need fixing in 7.3. They cause real problems for agencies, developers and large-scale WordPress sites, and they've been open for too long.
- Add specific capability for Navigation permissions #65881
- Nav block use slug to reference Navigation Menu #45512
- current-menu-item does not get applied to custom links in navigation block #61266
User Stories
As a site owner, I want editing my menu to work the way I expect, so I can update my site's navigation without needing help.
As a contributor, I want each change backed by user testing before it ships, so we can be confident it solves the problem rather than creating new ones.
Activity
[-]Tracking: Improving Navigation Editing in WordPress 7.3[/-][+]Improving Navigation Editing in WordPress 7.3[/+]frspp commentedon Nov 17, 2026
Do not agree:
not sure what you mean, adding a submenu? Yup seems not possible in that previous screenshot, but when in the proper block editor is easy, imo workflow is good.
Sorry but the first screen in that time somehow reminds me about Elementor, which is very horrible and should not ever by used.
jhmonroe commentedon Nov 19, 2026
@getdave the nav toggles are a great feature! one of the most annoying things about the standard nav editor is that it's everything or nothing in a way... all page lists (which I never use, who does?!) or tedious manual creation one by one