Drupal Architecture

This is a brief description of major site features and how they are handled in Drupal architecture terms. We have highlighted areas here where some additional specification is needed.

Projects:

• Moblin projects are implemented as Drupal organic groups with standard description and a "project shortname" for git integration.
• The project-types are implemented as a taxonomy vocabulary.
• Project maintainers are group admins.
• Group members can receive email updates when new blogs, documentation or downloads are posted
• Projects are automatically added as "root" book nodes (see documentation for details)

Downloads

• Download are their own node type with links, release notes, and version numbers.
• Additional fields may be needed to handle download status, weight, etc. Needs more speccing.

Documentation

• Documentation is implemented as a drupal "book" type, allowing for hierarchical organization
• Documentation is also implement in wiki-style: open to edits, retaining revisions, and utilizing "freelinking" to allow quick interconnection of pages, allowing for organic organization
• Documentation posted as part of a project is automatically placed into the project's book tree

Verticals

• Verticals are implemented as a administratively-defined taxonomy vocabulary.
• The ui for selecting verticals will be themed into checkboxes with icons

Landing Pages

• The main landing pages are implemented as a custom node type.
• They will have a specific tpl.php file for custom theming.
• They will also include an "attached view" so that a list of content can easily be appended.

Vertical Landing Pages

• Vertical landing pages are implemented as a custom node type.
• They will have a specific tpl.php file for custom theming.
• Vertical landing pages take over the right sidebar.
• They will also include some ui for adding various blocks from the system into this internalized sidebar.