Performance

Tutorial of Alpha 4 in action
HTML Export allows you to take your Drupal site and select paths from it based on criteria to export to HTML. It supports OG, results from Views, per content type, all menu router items, and all nodes as default criteria for publishing to html. Developers can extend and override these selections through a simple hook / api system. This module requires that Simple HTML Dom module/library be installed to help with the parsing of the html being created.

Drupal 6.x-2.x

Special note: The Base URL ($base_url) MUST be set in your site's settings.php file in order to use this module.

Features

• API hooks able to add / define / prune / alter the paths, assets, and html data used in export
• Supports ANY drupal path, not just nodes
• Ability to remove DOM elements in bulk during page export (follows convention div[id=admin-toolbar] to remove admin module output)
• New publishing metric to make creation cleaner (folder stacking instead of flat nodes)
• Batch API to avoid timeouts and be able to handle massive sites
• Selection criteria hooked in through API
• Selection criteria hooked up to views queries

MailQ is a module that queues ALL mails originating from a Drupal site into a queue and then processes this queue and sends mails in batches during cron runs. However, it still uses drupal core or other modules like Mimemail to actually send the mails.

Update: A new release 6.x-2.0-alpha1 is now available. Download and try.

This module is a set of base component and connectors to integrate Doctrine ORM with Drupal Core. The Doctrine Object Relational Mapper sits on top of a powerful database abstraction layer (DBAL). One of its key features is the option to write database queries in a proprietary object oriented SQL dialect called Doctrine Query Language (DQL), inspired by Hibernates HQL.

http://www.doctrine-project.org/projects/orm.html

This module provides integration with Doctrine ORM, giving developers a powerful alternative to SQL that maintains flexibility without requiring unnecessary code duplication.

Designed with a few goal in mind:

• Maintainability: the software will evolves with the Doctrine library and with versions of Drupal, the code base is written to cope with a changed environment. Test suit is the same quality as the software itself, allowing the isolation of defect for further correction and ensure new requirements will not break anything, thus, making future maintenance easier.
• Dependability: it does what it claims, and is trustworthy. The code is optimized to run for limited resources computers with special care to cache optimizations or any form of I/O which are costly.

The aim of the JavaScript Aggregator module is to improve performance of your site with less server requests and bandwidth per page. In Drupal 5, all the JavaScript files will be aggregated into one file and optionally minified. JavaScript aggregation was brought into core with Drupal 6, so the Drupal 6 version of this module goes one step further to minify that file.

It basically does the following:

• Takes the $scripts variable and removes .js files using a regular expression
• Generates a unique filename for any set of .js files
• Creates and caches one file containing all .js files in files/js
• Optionally minifies the JavaScript using JSMin
• Returns a modified $scripts variable with link to cached file

This module provides easy Content Delivery Network integration for Drupal sites.

Node Hierarchy allows nodes to be children of other nodes creating a tree-like hierarchy of content. The module offers:

• 1-Click creation of hierarchical menus
• Hierarchical breadcrumbs
• Automatic hierarchical urls using Pathauto (and token module)
  (eg: q=aboutus/history/beginning).
• Automatic creation of hierarchical menus if desired.
• Optional Views integration.
• Optional Node Access integration.