First, drop-buttons are awesome. So happy to see these proliferate throughout core UIs! :)
However, if we are going to "hide" a bunch of the less-used administration links inside the drop-button, we need to make sure that the top one, the "most commonly used" one needs to be correct choice (or as close as we can get it). This issue is a place to track all the drop-buttons in core that need to be changed.
- Put the most-used op first.
- Sentence-case the dropbutton links.
- Make dropbuttons consistent with contextual links, tabs, etc.
- Put the useful things in dropbuttons.
- Make a call on whether delete ops should ever be in dropbuttons
| DropButton | 1. Good default | 2. Sentence-case | 3. Consistent | 4. All the things | 5. Delete op? |
| Blocks | y | N | ? | ? | ? |
| Contact | y | y | y | y | ? |
| Content Types | y | y | y | y | ? |
| Fields | y | y | y | ? | ? |
| Block Types | y | y | y | y | ? |
| Menus | y | N | y | y | ? |
| Menu Items | y | y | y | y | ? |
| Vocabulary | N | N | N | N | ? |
| Terms | y | N | ? | ? | ? |
| Views | y | y | y | y | ? |
| Content | y | y | ? | ? | ? |
| People | y | y | ? | ? | ? |
| Themes* | N | N | N | N | ? |
Related issues
#1824634: [meta] Dropbutton accessibility issues
*#1973322: Add drop-buttons to the appearance page