Voting starts in March for the Drupal Association Board election.
The information architecture of Drupal 7 has changed significantly from previous Drupal versions. Drupal 7's user interface includes the following administrative sections:
This handbook page will explain where to place a module's configuration within these sections. Each section's base Drupal path is also given (for use in hook_menu()).
The Content section lists all nodes. No module should add its configuration here. Only lists related to node objects should be included here.
Examples:Lists of comments
The Structure section is for important modules used to build the structure of a website. It includes most of the old "Site Building" category from Drupal 6. The intent is to keep this section small. It would contain only very important site building modules such as Views and Panels.
The Appearance section holds settings specific to themes. No module should add any configuration here unless it is related to an installed theme.
The People section should only be used for the listing of users. Modules may expose other data here. For example, a module might list events related to each user.
However, no module should add its configuration here. Instead, use the People category under the Configuration section (below).
Examples:Lists of events related to users, signups
The Configuration section is for all configuration. Any module which exposes configuration should be placed here. The category for a module's configuration should be chosen carefully.
Avoid creating new categories. Instead, consider placing your module's configuration near a related module. If possible, add the module's configuration under one of the following categories:
- Content authoring
- Regional and language
- Search and metadata
- Web services
- User interface
The People category should hold all modules that would fit under the old "User Management" category in Drupal 6. (Note: Do not confuse this category with the People section above.)
Examples: Access control modules
The System category should hold all modules that deeply affect the system but expose no actual functionality to the site user.
The Development category should hold any module which is primarily for developers.
The Content authoring category should contain any modules related to how users submit new and edit existing contents on the site.
Examples: Text Formats, Mollom content moderation
Regional and language
The Regional category should hold any module which affects the geography-related and localization settings of the site.
Examples: Date and Time, Languages, Translate Interface
Search and metadata
The Search and metadata category is mainly for modules dealing with machine-readable abstraction of site's content.
Examples: Search Settings, URL Aliases, Clean URLs
The Media category contains modules with effect on how Drupal deals with files and processes images.
Examples: File System, Image Styles, Image Toolkit
The Web services category is for modules which connect a Drupal site with external data sources or services. Examples include RSS feeds, authentication providers, payment gateways, etc.
The User interface category should hold all modules specifically aimed at enhancing or changing a particular interface. This includes both interfaces for end users and those for administrators.