You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue captures the current priorities for Navigation which we are aiming to include in WordPress 6.2.
Some progress has been made in 6.1, particularly on the theme switching, fallback and new menu facets. Editing menus is now an area that now requires attention.
There's also a longer backlog used to more exhaustively track open issues, bugs, and pending tasks at #38275.
Editing Menus
There are other questions around how to normalize things like "page list" (automated list) and individually curated items, how we handle transitioning from one to the other mechanism, etc. The flows for managing a menu extend beyond the menu itself (as in, it also needs to be taken into account when creating content like pages) and that's important to recognize.
This issue captures the current priorities for Navigation which we are aiming to include in WordPress 6.2.
Some progress has been made in 6.1, particularly on the theme switching, fallback and new menu facets. Editing menus is now an area that now requires attention.
There's also a longer backlog used to more exhaustively track open issues, bugs, and pending tasks at #38275.
Editing Menus
There are other questions around how to normalize things like "page list" (automated list) and individually curated items, how we handle transitioning from one to the other mechanism, etc. The flows for managing a menu extend beyond the menu itself (as in, it also needs to be taken into account when creating content like pages) and that's important to recognize.
This work for 42257 can be broken down into discrete pieces, some of which can be done in parallel. These in a rough priority order:
At this point we can do some user tests
The text was updated successfully, but these errors were encountered: