Hey so looking more closely at the labels and categories, I think they need the following juggling and want to get some consensus that what I am saying makes sense.
The categories Daniel put together are better than the labels currently assigned to plugins by their developers (IMO, but please disagree if you do)
But, because Daniels good labels only apply to ~70 of the 1000+ plugins we still need the other labels
Having both labels and categories appear in the UI and overlap the way they do is totally confusing.
...so I want to merge the two lists, starting from Daniel's list and mapping it back to existing labels as follows...
(Daniel good categories) =vs=> (plugin labels)
Show all plugins ===> reset all filters
SCM Connectors ===> scm
Build and Analysis ===> (let's split this into 2 categories)
Build Containers ==> 'builder' and 'buildwrapper'
Reports and Analysis ==> 'report'
Deployment ===> 'upload'
Pipelines ===> stays as it is, because tags don't really capture this guy correctly
Container ===> same as above
Mobile (this would be new) ===> 'ios' and 'android'
Users and Security ===> 'users' and 'security'
General Purpose ===> all other labels not otherwise mentioned above
When "General Purpose" is selected, we would then show the remaining labels as sub-filter options
Daniel's list, by virtue of the fact that he categorized those plugins, also gives us the added metadata of 'approved for initial install' which would be nice to also surface and potentially add as a binary filter that could be layered atop the above categories (but if this is controversial in any way, forget I asked).
To help make this clearer, here is a video with my work-in-progress:
...still a decent amount of Ps and Qs clean-up to do, but I would like to get at least some of you-all's feedback on the above.
Here is the PR: https://github.com/gusreiber/jenkins-plugin-site/pull/8