Problem/Motivation
There are too many items on the Structure page (/admin/structure) for a flat list. It is hard to find a particular link.
Steps to reproduce
Proposed resolution
Group together all the items for configuring entity types (block types, content types, media types, taxonomy, etc.).
Remaining tasks
User interface changes
Change the page at /admin/structure.
Before
Here is the current page, using the Umami demo profile:

API changes
None
Data model changes
None
Release notes snippet
TBD
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | structure-page-mockup.png | 85.71 KB | benjifisher |
| structure-page-umami.png | 94.21 KB | benjifisher |
Comments
Comment #2
benjifisherWe reviewed #2985887: Make core's structure descriptions more consistent at #3355631: Drupal Usability Meeting 2023-04-28, and decided that a better solution to the problem of inconsistent descriptions is to group together the links for configuring (fieldable) entity types. Referring to the screenshot (Umami) in the issue description, more than half the links belong in this group:
If we create that group and add some static text for the group, then we will not need descriptions for the links in that group.
One possibility for the group label is "Content structure".
Here is a mockup of the page after adding the new group:
Any link that does not belong in this group will be displayed in a separate list. TBD:
At first, all links on this page from non-core modules will go in the "other" group. Once this feature is implemented, other modules that create entity types should be able to update their links so that their links go in the appropriate group.
Once we finish this issue, we can consider adding additional groups.
Before adding this issue, I found #2518960: Emphasize the most important items on the 'structure' page. It looks to me as though no one reached consensus on that issue. At least one comment there points out that "important" vs. "unimportant" is not a viable distinction, and I agree with that. I think the proposal in this issue is more incremental and easier to implement than the ideas discussed there.
Comment #3
aaronmchaleI would recommend "Structured content" rather than "Content structure", as that's more of a generally used term (at least it is 1among people who work in content design type roles).
Comment #5
mstrelan commented-1 from me. Not sure when 9 items became too many. Having to figure out which group an item is in would be more cognitive load than scanning the 9 items listed alphabetically.