Let's remove some noise and make Drupal easier to digest and user. In Views, I introduced drop buttons because 80% of the time, users are adding fields. 20% of the time, they're sorting, deleting, etc. This pattern applies to all of Drupal.
- /content: 80% task is to edit, so push delete into the dropbutton
- /blocks: 80% task is to configure, so push delete into the dropbutton
- /structure/types: 80% task is to manage fields, so push edit, delete, manage display into the dropbutton. If we must, keep manage display as it's own button
- /taxonomy:80% task is to list terms (add could be too, but you can add under list), so push edit vocabulary, add terms into the dropbutton
- /menu: 80% tasks is to list links (add could be too, but you can add under list), so push edit menu and add link into the drop button
- /modules: might be the exception as permissions and configure are on the same playing field. If we had to decide, configure is probably more used than permissions.