Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Drupal modules exceed 150 from a quick count, impressive.
The drawback of this success is that it is becoming increasingly difficult to examine available modules, know what is out there. Often, there are messages on the forum with an individual asking, "is there a module that..."
Perhaps a taxonomy for modules could be developed and applied, allowing for organization by category? Maybe similar to the display and user organization of listings by Category for Issues.
Such a scheme may improve module visibility and user access.
Comments
Comment #1
moshe weitzman CreditAttribution: moshe weitzman commentedmost everyone agrees that a vocabulary is welcome for modules. please make suggestions and discus the benefits and risks of your proposal.
Comment #2
Carl Ditzler CreditAttribution: Carl Ditzler commentedModule Vocabulary
Benefits
Use of categories would present a organizational method to a long list of available modules and a user may feel overwhelmed by such a large list. By selecting a category appropriate to his or her needs, a user may view or sort only relevant modules, thereby improving the likelihood of a user finding a suitable module.
Risks
Initial category association with a module would likely be required by a maintainer/manager of a module; such association is likely subjective and a person may not select a category that is not as intuitive as one selected by another person. A module, furthermore, may be more difficult to locate than the current method (a single list). Currently, all modules are located on one page and user may find a module with keywords inserted into a browser "Find" feature. If modules are only displayed by a selected category, a user may not see/find a module if a module is not present in a category he/she feels it should be associated with. Also, a list of categories may be as exhaustive as a list of modules, given module diversity.
Suggested Vocabulary
The following list is merely a suggestion and modifications are expecte; there are likely terms better than those presented. Each proposal includes possible associated modules and not all modules are included on this list. Possible associated modules are meant to provide examples per category. Also, it is assumed multiple category associations will be used and it would be difficult to include a method of categorization for modules without multiple category selection because many modules cross various functionalities
(See Full Version for Suggestions)
Comment #3
sulleleven CreditAttribution: sulleleven commentedthis would rid of headaches. I always scan the entire list to see if anything new appears....
would be very helpful...
and... to have a category for 'new' additions, say within 1 month or so.
Comment #4
Carl Ditzler CreditAttribution: Carl Ditzler commentedPerhaps vocabulary should be added for Drupal versions.... in addition to a module's category? For instance, if foo.module is a Calendar and Events module compatible with Drupal 4.5 and 4.4, then it would be associated with Calendar and Events, 4.5, and 4.4. If so, modules could be organized by Drupal version and a user may see modules only compatible with a recent version.
Comment #5
alexn CreditAttribution: alexn commentedJust as important would be a taxonomy for development status. These are from Sourceforge:
1 - Planning (14850 projects)
2 - Pre-Alpha (11344 projects)
3 - Alpha (11464 projects)
4 - Beta (14562 projects)
5 - Production/Stable (12174 projects)
6 - Mature (1098 projects)
7 - Inactive (1053 projects)
Notice that perhaps 1/5 of projects on Sourceforge are considered "stable." It would be nice to know which 1/5 of the Drupal modules are stable.
Comment #6
clairem CreditAttribution: clairem commentedI think I would like to see multiple classifications for modules, using all the suggestions so far:
Ideally the whole thing wpuld be searchable in the same way as the issues base, and linked to it, so that users can see what is happening with a module.
Comment #7
freyquency CreditAttribution: freyquency commentedPerhaps fewer categories? I don't like looking over the whole list all the time either, but I'd prefer if it fell into larger categories instead of very specific ones.
(ps - you can get rss feeds of the categories - ie-modules... makes it super easy to know when new stuff is out. check out - http://drupal.org/node/16489 for a list.)
Comment #8
puregin CreditAttribution: puregin commentedIt would be nice, in any case, to have module descriptions include a 'See Also' section. This could be used to direct readers to similar, complementary, or otherwise related modules.
Comment #9
zilla CreditAttribution: zilla commentedgreat ideas...couple of quick ideas as an information organizer, not a developer:
it would seem that this could be done quite easily and quickly with the site_menu module, create a vocabulary for modules and add terms for the types (e.g. syndication, ecommerce) and then perhaps a second vocabulary for module release (4.6 or 4.5 etc) and another for development stage and so on..perhaps also using sitemap and limiting to just specific vocabulary views?
this would pull up a list of modules and each would be labeled...
then anybody could use 'related terms' to associate one type of module with another category, or see where there is an instance of one module across two vocabularies...
...and then perhaps use that nifty 'notify' module but constrained to the vocabulary to get critical updates?
not sure, just some gut reactions...seems like there are a LOT of great modules within drupal that drupal.org is not even using and might be well served by...for example, 'side content' could show a nitwit-proof list of related modules, but that would be manual...or 'series' could show the modules within their respective vocabs..and so on...
any thoughts?
Comment #10
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedCategories are now available.
Comment #11
(not verified) CreditAttribution: commented