- Issue created by @pameeela
- 🇳🇱Netherlands ifrik
This idea had come up previously as issue 📌 Add "Add" item to toolbar. Needs work including input from the UX team.
Some questions that had come up with that:
- Do content creators need to know what entity type they are creating? Or do they just need to know how it's called on their site?
- How does it look if there are so many items that list is longer then the screen?
- Contrib and custom modules should also be able to add their links into the list. - 🇦🇺Australia pameeela
I’m not totally sold on the grouping idea, that was proposed in the other issue. I guess I don’t have the solution, just raising a concern about the current UX.
I myself find it hard to parse even the shortest list to find the content type I’m after. But I'm willing to concede that this is just because it’s a change and new users may not find the same.
- 🇳🇱Netherlands ifrik
Some more thoughts after having discussed this with some people at DevDays:
- If the items are not grouped then they would need to be listed alphabetically - rather then having them sorted by type but without disclosing that to the content creator. Without headings to group them, that just looks like a scrambled random list. And as in the issue description: some are used so rarely that it looks more like clutter..
- Grouping them by type and using that as a heading (node/content, media, user, taxonomy term etc.) provides some structure, and a way to break down long lists. But does the content creater need to know what is what entity type?
- On many sites, different types of content might belong together. For example, on a site that displays information about conferences, the content creator might need to create a node for the event, several speaker profiles, a taxonomy term for the city and a custom geo entity for the venue. Grouping them together would improve the UX for the content creator, and as site builders we can configure that for them. It can't be standardized, but grouping by type looks and works nicely out of the box, then we can just change it for the individual site. (Even if it requires some content export for the new menu items.
Note: this is not for the look and feel but an example, how menu items could end up on specific website if grouped for the content creater UX. - 🇨🇦Canada mandclu
Further to the previous comment, the Type Tray module → does allow for grouping content types into categories. Maybe there's a way to leverage those groupings in the menu?
- 🇬🇧United Kingdom catch
Redirect and media bundles don't really belong here IMO.
Redirects are content entities, but they're not site content, and they're usually created silently by pathauto, creating manual redirects is much more of an edge case.
Media entities are usually (but not exclusively) created via the media widget on other entity types.
I also personally wouldn't put 'User' here either since there can be sites where a user is never manually created.
If all of these were gone, the list in the issue summary would be very short, and then categories might not be necessary at all.