I want to propose few more taxonomies for modules. I miss the ability to search modules by the information if they provide an API or if they're only implementing one. For example you now have Drush and modules which provide Drush commands in the same category Drush. Or the in Views category, first is Views, second Page Title, which main purpose is slightly different. How to browse Views plugins/handlers effectively? Or is the answer to this a hierarchical tree of categories?

Other taxonomy can hold the information about modules purpose. If they're for site builders, developers, ...

A footprint information can be useful - small, normal, large, ...

Comments

mgifford’s picture

mgifford
he/him
Primary language English
commented
Project: Drupal.org infrastructure » Drupal.org content
Component: Drupal.org module » Services listing
Issue summary: View changes

As the number of modules has grown in d.o, this has become even more important.

I do think this would make sense to implement.

I think it's more of a content issue though, so moving it.

lizzjoy’s picture

lizzjoy
she/her
Primary language English
Location Ann Arbor
commented
Component: Services listing » Other

@wapnik, thanks for the suggestion. Can you propose specific taxonomy vocabularies and terms?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

I am closing this due to lack of feedback.

Maybe a couple of vocabularies instead of one would help, but we need to decide which aspects of a project should be exposed at taxonomy terms.

Please feel free to re-open this issue if you have a concrete suggestion of what vocabulary should be added to the already existing category vocabulary.