I am by no mean a UI/UX expert but anything that simplifies finding the items I’m looking for is a win in my book.
One of the things that is incredibly frustrating though (from an admin perspective) is the convoluted mess we have today with every plugin author doing something just a little bit different.
If you have multiple plugins installed, from multiple vendors/ authors then the chances are one plugin uses radio buttons, another plugin uses check boxes, another uses sliders.
Some default to having options turned on, while other default to having options turned off.
I have to consciously remember does selecting an option actually enable a feature or disables a feature instead.
Maybe ClassicPress should enforce a whole settings paradigm where ClassicPress could provide a UI framework not just for security settings, but also for other general settings. Then plugin authors could interface with that framework.
Where a plugin’s settings becomes a child object of the parent CMS settings?
That way you could enforce some uniformity and UI/UX standards behind the scenes.
Plugin authors could still have their “promotions” but they would be confined to their plugin settings “tab” or page or what have you.
For that matter maybe it’s worth adding to core an API for displaying different (and STANDARDIZED) types of alert messages (Info, Warn, Error, Debug, etc. with an optional minimum role to show the alert to) to the admin that plugins could call so they all don’t have to roll their own too. Again just a thought.
But as for providing just a link on a page? I don’t think that would be very helpful.
The vast majority of plugins have no specific security settings, unless you’re actually talking about a *press “security” plugin like WordFence, etc.
Just my $0.02.