Actively maintained

Summary

The TEI Search module adds search functions to the TEI Content module. Its key feature is that it is aware of some TEI tags.

The TEI Search module is part of a package of modules called TEICHI framework. This name brings together the Text Encoding Initiative (TEI) and Computer-Human Interaction (CHI). This framework functions in a Drupal 7 environment and consists of three modules: TEI Search (described here, still in development), TEI Content (the base module: currently at http://drupal.org/sandbox/christof.s/1118172), and TEI Download (currently at http://drupal.org/sandbox/christof.s/1120822).

Summary

The TEI Download module allows downloading various renderings of documents encoded according to the standards of the Text Encoding Initiative (TEI) and published with the TEI Content module. The TEI Download module lets the user download the documents displayed online in several file formats (txt, epub, xml/tei) and several versions.

The module is part of a package of modules we call the TEICHI Framework. This name brings together the Text Encoding Initiative (TEI) and Computer-Human Interaction (CHI). The package works with Drupal 7 and consists of three modules: TEI Download (described here), TEI Content (the base module, currently at http://drupal.org/sandbox/christof.s/1118172), and TEI Search (in development, currently at http://drupal.org/sandbox/christof.s/1120932).

Overview

This module allows you to upload an image in the menu-item's configuration form and use the image anywhere in your theme. This is useful if you want to display an image - that is related to a menu entry - somewhere in your theme (header, navigation).

Based on david DeSandro's "jQuery Masonry" script, this module provides a Masonry style view. Masonry is a layout plugin for jQuery. Think of it as the flip side of CSS floats.

This is simply a file (drupal-check.php) to upload and view on the server to test if the current setup meets the requirements to for a base Drupal install.

A unique set of tools used for Services 3.x.

Currently services_tools houses two modules.

• Historical
• Definition

You can see them below.

Historical

An API for providing historical versions of a Services API. Any quality services implementation should be versioned to ensure incompatibility issues do not arise. Even a simple API used internally between two machines can benefit from versioning since it will allow the machines to be updated independent of one another. For full fledged public APIs versioning is also essential to ensure the stability of the service.

Instead of always pointing clients to the current API, use a version number even if there is only one. For example, api/foo becomes api/1.0/foo. This ensure that when you make changes and create api/1.1/foo that clients using api/1.0/foo continue to work and can upgrade at their leisure.

The API is quite flexible and provides a number of ways the historical API may be implemented. For details see services_historical.api.php and the original issue which describes the thought process.