- Issue created by @rkoller
We were discussing ✨ Warn user when entity delete will cause menu item re-parenting Needs review in today's usability meeting 📌 Drupal Usability Meeting 2024-02-16 Active . The latter issue will have a link to a recording of the meeting. For the record the attendees of the meeting were @AaronMcHale, @benjifisher, @rkoller, @simohell, and @worldlinemine
If you take a look at a site that is set up with the Umami demo profile and you go to /en/admin/structure/menu/manage/main, out of the box you have Home, Articles, and Recipes as menu links. If you add another link, let's call it Test and you compare the list of available operations for the different menu links you will notice the following:
Home
Edit
Add child
Test
Edit
Add child
Delete
Articles
Edit
Delete (see
🐛
Menu links created by a view have a visually and functionally broken delete option
Active
Add child
Recipes
Edit
Delete (see
🐛
Menu links created by a view have a visually and functionally broken delete option
Active
Add child
Problem is without consulting the options of the button in the operations column there is no way to distinguish or even realize in the first place that there are different types of menu links with a different number of options available. At the moment the list of menu links is uniform, their category is only implicitly communicated by the number and type of operation options available. But in fact you have menu links created in code, you have menu links created in/by Views (technically also in code at least for the Umami example) and you have menu links created manually within the admin ui.
1. Install Drupal 11.x-dev with the demo_umami
2. Go to /en/admin/structure/menu/manage/main
3. Create a new menu link called Test (/en/admin/structure/menu/manage/main/add?destination=/en/admin/structure/menu/manage/main)
The idea was to follow the pattern used on /en/admin/structure/block and introduce such a category column for menu pages as well.
- Decide which categories to create and how to name them