The content api module is a resource for Services 3.x in Drupal 6. Content API exposes a new 'content' type resource to Services which implements an index and retrieve functions for nodes. The index function allows advanced querying of nodes to match selected criteria.
An entity collection can be used as a replacement for Node queue that works for all entities.
Entity collection has pluggable backends for storage. It comes with a DB backend but you can write your own backend for storing the entities. You select your preferred storage backend per bundle.
Entity collections are fieldable so you can add metadata to your collections (like descriptions and whatever you want).
The emergency module allows you to override the normal layout and content of your site in the event of an emergency. It is primarily designed for institutional websites (such as universities), but could be used by any site that needs to broadcast urgent information to visitors.
By declaring an emergency, non-essential block regions can be hidden and information related to the emergency (such as contact numbers) can be shown instead. This gives critical information more visibility, and allows you to quickly disable non-critical, bandwidth-intensive content to better endure increased site traffic. You can also define multiple emergency levels with different sets of overrides. For example, you could have a "closure" level that is used to declare a campus closure due to inclement weather, and a separate "public safety issue" level for life-threatening situations.
The development of this module continued at https://www.drupal.org/project/high_contrast
Provides a quick solution to allow the user to switch between the active theme and a high contrast version of it.
This high contrast version is automatically generated adding a stylesheet which overrides the defined CSS rules.
The Content Page module allows requests to pages in your Drupal web site to be rendered with just the content area visible. This allows pages to be displayed in an iframe using modules like Shadowbox without too much work.
The main module just provides a hook to allow other modules to flag a request so that only the content will be displayed. There is a sub module called Content Page AJAX Request that will flag any request where $_GET['ajax_request'] is set to show only the content.
This module provides an easy way to indicate which menu item is active adding the active CSS class depending the path that the users are seeing.
IMPORTANT
This assumes they are using theme('menu_link') for the menu rendering to html.
FEATURES
ImageAPI toolkit using powerful and high-performance GraphicsMagick command line tool.
Imagecache works great, and the idea of this simple module is to let you to use a second url (static) to share the images build by imagecache.
This module lets you use a second domain as a cdn to download faster the full website, http://developer.yahoo.com/performance/rules.html
With this module the Yslow (firefox pluggin) gives you really good news about your website ;).
Defines special tags for the imagefield module to show images in document body.
You just use [gallery] tag with parameters in your document body to show image field images where you want in the document body and so as you want that(e.g. put image into thickbox or somethig else).
Module description is placed here: http://brainstorm.name/node/399.html
Simple module which allows look links to nodes, taxonomy terms, pages - with ".html" suffix.
Without using custom path or pathauto path to your node will look like /node/1234.html.
Path to taxonomy term - /tags/396.html instead of /taxonomy/term/12345
And thing, many people looking for: pages with page numbers - without ?page=123
They will look like /page/1234.html
For example instead of /node?page=2 you will see /node/page/2.html
For future I think how to make suffix customizable and make wiki-like work of drupal for some node types.
