Skip to content

Navigation Menus: Let my menu follow my pages until I need to manage it myself #86939

Open
0 of 2 issues completed

Description

@getdave

What

Improve the current Menus system so that:

  • people's menus show their pages by default
  • keep up as they add /remove pages
  • they can understand how to switch to a menu they manage themselves when they need to
  • they understand the implications of moving from "auto" to "manually managed".

...all without needing to understand how WordPress builds the menu (e.g. blocks).

The complexity of the underlying system should be obfuscated in favour of goal centric, user orientated concepts and wording.

Why

Today, a new Navigation block shows a Page List block, so there's always something in the menu, in the editor and on the site.

To change that menu, people have to understand what a Page List is, find its "Edit" step and accept that it becomes a list of separate links in a saved navigation menu.

People see a strong link between their pages and their menu. For most sites, the menu is their pages. As a site grows, that may become "only some of my pages" (and/or also other types of links), but the starting point is the same.

The Page List default supports that, but it exposes how the framework works. Page List, converting it and the wp_navigation post that results are implementation details, yet people meet all of them the first time they want to change their menu.

Existing sites

Many Navigation blocks and menus in the wild today use the current Page List default. Any change needs to give those sites a good experience too, not only new ones. People shouldn't have to rebuild or migrate their menu to benefit.

How we'll know it's working

  • In user tests, people can tell that their menu shows all their published pages, without being told.
  • A page someone publishes shows up in their menu without them editing it.
  • People can customise their menu without being shown how, and can explain what will change before they confirm.
  • Sites with an existing Page List menu get the same improvements, without rebuilding their menu.
  • No one needs the words "Page List" or "navigation menu post" to complete these tasks.
  • People can complete these tasks just as easily when editing a Navigation block inside a template or template part, using the List View tab in the block's inspector controls, as they can on the Navigation Menus screen in the Site Editor.
  • People can tell from the Navigation block in the canvas that their menu updates itself as they add pages, not only from the list view or the Navigation Menus screen. This applies whichever approach we take, an Auto menu or auto-adding new pages.

Ideas

Related

User Stories

As a site owner, I want to see that my menu shows all my published pages, so I know what my visitors will see.

As a site owner, I want new pages to be added to my menu as I create them, so I don't have to manage my menu separately until I need to.

As a site owner, I want to change my menu without learning WordPress concepts like Page List, so updating it feels simple.

As a site owner, I want to move from a menu of my pages to one I manage myself when I need to, so I can build a menu that fits a more complex site.

As a site owner, I want to understand what changes when I start managing my menu myself, so I can make that choice with confidence.

As a site owner with an existing site, I want my current menu to get these improvements, so I don't have to rebuild it to experience a good UX.

As a site owner editing my header or footer, I want to see on the canvas that my menu updates itself, so I know how it will behave without opening another panel or screen.

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