Skip to content

Navigation Menus: Replace "Add block" with a task-based inserter #86177

Open

Description

@getdave

What

Adding anything other than a Page to a Navigation Menu today means using the block inserter. The button says "Add block", and from there people need to know which block type does what they want.

This issue proposes replacing that with a small, task-based menu that offers three plain choices:

  • Add an existing Page
  • Add a custom link
  • Add a sub menu

A "More..." option sits underneath for less common items, which leads into the bulk add screen (#86179).

A prototype showing the menu's add button opening a menu with Add existing page, Custom link, Submenu and More options

🎥 For context, watch this part of my prototype walkthrough video, from 21:38. The Navigation Menus section, from 17:05, covers how all of these ideas fit together.

🧪 Try it yourself in the working demo in WordPress Playground. The demo code lives in #86188.

🔌 This flow is now in the Create Not Learn editor plugin, where you can try it in WordPress Playground alongside the other menu changes. There's also a newer walkthrough of it, from 21:24.

Why

People don't think in blocks when they're building a menu. They think "I want to link to my Contact page" or "I want a dropdown".

In Automattic's user testing, people couldn't find how to add anything other than a Page. Nothing on the "Add block" button tells them it's possible.

Three plain options cover almost everything people add to a menu. The everyday case should never require knowing which block to pick.

How

  • Swap the "Add block" button in the Navigation Menu editing surfaces for a dropdown of task-based actions.
  • Apply this in both places the menu list view appears, on the Navigation Menus screen in the Site Editor and in the List View tab of the Navigation block's inspector controls. People should get the same experience wherever they edit their menu.
  • Each action maps to an existing block underneath (Page Link, Custom Link, Submenu), so nothing changes in the saved markup.
  • Keep the full range of options reachable through "More...", rather than removing them.
  • Check how this fits with the Link Control omni-search work in Navigation LinkUI: Include blocks and all entity types within search results #76803. The two could complement each other, with the task choice deciding what gets inserted and the search finding the content.

User Stories

As a site owner, I want to add a link to an existing Page with one obvious choice, so I don't have to learn what a block is to update my menu.

As a site owner, I want to add a custom link or a dropdown from the same menu, so I can build the menu I have in my head without hunting for the right block.

Video

video-inserter.mp4

Activity

  1. jeryj commented on Nov 2, 2026

    @jeryj
    Contributor

    I'm torn on this one. Now that the link control search can search blocks and other post types, what if we change the default suggested options to include common things like the Submenu appear at the top of the default results? That way they can immediately arrive in the search and not get slowed down with the happy "search for thing" path, but still get some initial options that show the common options.

    If we do with this route, I think we should at a minimum use Add page and not "Add existing page" as the Link Control there still offers a "Create page" option.

  2. getdave commented on Nov 6, 2026

    @getdave
    ContributorAuthor

    Whilst I love the improvements to the existing link control search, I'm not convinced its the right tool for users adding menu items.

    That said I can see the arguments the other way too.

    The correct approach is to take

    • my prototype
    • a prototype you have made of the ideas you proposed

    ...and then test these with users to see which one allows them to most effectively build different types of menus.

    I do note that of the many menu building UIs that I've looked at on other platforms, I haven't yet encountered one that relies on search. That said I'm very prepared to admit I'm wrong and will happily submit to the results of users testing.

    Would you be up for running a user test and reporting back?

  3. jeryj commented on Nov 7, 2026

    @jeryj
    Contributor

    Yes, let's definitely user test!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions