Content display

Recently read allows site administrators to enable blocks displaying a history of recently read content (nodes) both to anonymous and authenticated users.

Generates additional core elements/structures for the Style Guide module to help themers create more consistent Drupal themes.

Node CSS uses node fields to populate a CSS template file. CSS for all nodes can either be aggregated into a single file or generated per node. In both modes, the CSS files are added using drupal_add_css() so it complies with full Drupal aggregation and compression. If aggregation is turned on in Node CSS it is recommended to make the CSS node specific via a body node class because the same CSS file is loaded for multiple nodes. Many themes output a node specific class by default.

Full aggregation is recommended for performance (the same CSS file can be used across the entire site). Individual files is recommended for small sites and/or where you don't have access to a body node class.

body.page-node-<?php print $css_vars['nid']; ?>

Example applications

• Set an image uploaded into a node as a background image e.g. a body wallpaper or a flourish
• Set the background colour of a page element using jQuery Colorpicker

General usage

By default, fields according to the naming scheme field_css_ in enabled content types will automatically be passed to the template and hidden from the node display. Both the naming scheme and visibility can be changed.

This module provides an easy way to show the freely available weather images of the Hungarian www.idokep.hu website in a block.

Panels already has support for what this module wanted to do so I'm killing this project.

The taxonomy display module allows administrative configurable term display pages. This allows administrators to override the default presentation of taxonomy term pages per vocabulary through the taxonomy term page's manage display form.

Hook into taxonomy term pages

Taxonomy display exposes three plugin types for modules to overwrite portions of taxonomy term pages by providing their own plugins. These plugins are selectable on a per vocabulary basis, allowing the site administrator to decide which plugins they want to display for each vocabulary. To learn how to provide your own plugins see the developer resources page.

Selectable term displays

• Core

  • Plays nicely with Display suite.
  • Does not conflict with modules that make use of hook_taxonomy_term_view_alter(), hook_entity_view(), or hook_entity_view_alter().

• Hidden

Selectable associated content displays

• Core