Locate drupalisms that might create confusion among users

Updated through Comment 9 in issue comments.

https://www.drupal.org/project/drupal/issues/3381734

Also want to register a minor protest at calling 'taxonomy' a 'Drupalism' - it very accurately describes what it is, to the point that (to our amazement) it tested really well at the 2008 usability testing (unlike menus and blocks and... literally everything else), with the one disclaimer that some of the people we did testing with were university library staff. It's also a high-level concept in Wordpress

All other top level terms are nouns but this verb. (It sticks out). Short discussion should be had about why top level menu items have different name than the thing to which they relate.

I think d7ux added this and it was supposed to be a call to action, but 'Extensions' would be more standard. Except even that isn't really true because themes are extensions and they're in appearance. And it used to be admin/build/modules but it has the install profile listed so it's not really just modules either, although profiles are modules so it kind of is. There's also recipes and project browser coming up to deal with too.

it's a level of indirection to users/accounts, and it also contains the config for roles/permissions (which aren't people, or users, or accounts), see #2695771: Re-organise user/account items under admin/ for more.

In addition to catch's #1 point, the distinction between people, roles, users, permissions can get very foggy very quickly, especially because USERS are people who are authorized to login and *use* the system, whereas a "person" could be something like a staff content type node, where they have a Staff Listing, or something like that, but may not have an equivalent User privilege. Also, for Roles, something to the distinction that a user can occupy several different roles, so how does that impact their permissions? ie, if the user is a WRITER (can CREATE articles) and also a PUBLISHER (can PUBLISH and DELETE articles), then what are they actually allowed to do?

Short discussion should be had about why top level menu items have different name than the thing to which they relate.

Config is supposed to be for 'settings' and structure is supposed to be for 'structuring/building', but why are user fields under config when e.g. media fields are under structure? Similarly text formats, image styles, responsive images all feel like 'structure' but are also under config. This is partly a general IA issue but also I think config vs. structure is a terminological problem in itself.