By matt westgate on

As the Drupal site now plays host to over 120 contributed modules, it's become apparant that we need a new organziation system. Hey, why not use a taxonomy? Here is a schema based on the modules functionality to get the conversation rolling. For the sake of brevity i have not listed all modules. 

Drupal-contrib project taxonomy

# Content Types
  Modules that allow the creation of new content types for nodes and otherwise.
  
  article
  event
  glossary
  guestbook
  headlines
  recipe
  weblink
  

# Commerce
  Modules that pertain to buying and selling
  
  amazon
  e-commerce
  

# Community Extensions
  Modules that help site members stay informed and active.
  
  bookmarks
  buddylist
  chatbox
  private message


# Content
  Modules related to manipulating or syndicating content.
  
  annotation
  article
  atom
  banner
  breadcrumb
  catalog
  cloud
  compose tips
  doxygen
  externalpage
  feature
  flexinode
  htmlarea
  htmltidy
    

# E-mail
  Modules that deal with mail delivery and protocols

  checkmail
  ezmlm
  feedback
  form_mail


# Developer tools (see also drupal doxygen docs)
  Example code and profiling tools that teaches developers how to write modules.

  devel
  howto
  

# File management (see also image management)
  
  attached file
  cvslog
  file
  filestore


# Filters
  Modules related to filtering output
  
  agents
  bbcode
  dontshout
  filtercache
  fixentities
  htmlcorrector


# Image Management
  Modules to upload and manage images. Also includes galleries and manipulation 
  tools.
  
  image
  watermark
  inline_image
  gallery
    

# Navigation
  Modules that help you build navigational structures for your site. Also 
  includes other navigation aides for external resources.
  
  bookmark
  menus
  navigation
  weblinks
  forum link
  indexof


# Patches
  Modules that patch the core Drupal code.


# User Management

  authentication
  birthday
  groups