Examples of adding/moving admin menu items - contrib examples

1. A menu link to the Group configuration section
2. It does not manipulate anything, merely add to the admin menu
3. The Group module does more than just defining a new entity type or adding content; it takes the existing permission layer and adds a whole new level to it. Given this will affect the security of the website, I figured it would be too obscure when being split up into several screens under Structure, Content and Configuration.
4. The current admin menu works rather well for modules that add a single entity type with a specific purpose. For more complex modules such as Group (and Commerce for example), it makes it hard to find the right admin pages.

See attached screenshot of what it looks like. I figured it was best suited to have it sit right next to People, as both People and Groups define access across the site.

Context: I maintain a module that does single-sign-on (via SAML): users log into your Drupal site through an external 'identity provider' rather than the user/password screen.

1. Added a link to the configuration screen, at At Configuration > People.
2. Site-wide configuration settings for site admins, to make the module work.
3. This seems like the best place because it is about managing users and the way they are created/manipulated.
4. Nothing prevented us from placing it where we wanted but there was some contention about the position: Someone rewrote the module and put it at Configuration > Web Services instead. (There is a point to this: the single sign-on login flow is redirecting users to an external service.) The consensus with the original maintainer was to move it back.

So far, I haven't actually done D8 contrib just yet, but I think this can be answered also for custom module development also.

1. Menu link to a configuration
2. Manipulates the order of entities that is listed in frontpage (manual sort)
3. Under admin/content as an action tab
4. Not at this case, but we needed to be careful with the permissions that editors (what should access this menu item) would have sensible route to this configuration

Problems with adding more granular permissions

Issue #1975064: Add more granular block content permissions is an example that by adding pages as tabs (tasks) on other pages makes it difficult to add appropriate permissions.
Adding a separate permission to edit existing Custom block content, means that users need to be able to access the Custom block library page. It's possible to add a permission for that, but users still won't see any navigation (menu item etc) to get to the page because for that they need the permission to administer blocks (to get to the Block layout page) and in order to see that they need access to the whole Structure and Configuration section.

Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Since this was about gathering experience and there's been no follow up in 8 years think we are safe to close out. Am assigning credit to everyone.