Theme Enhancements

This very simple modules is for sites that have different seasons (summer and winter). In summer there might be a bright yellow theme, in winter a cold blue one. There might though also be different nodes in winter and summer. So what this module does is: Defining a winter and a summer theme and defining winter and summer nodes. So when the admin switches to the summer theme, the light summer css will be loaded and the user is being forwarded to the summer nodes.

This module is sponsered by www.previon.ch

The VPrint module will create an image (using the GD library) that prints text
vertically. The text and font size are specified as GET parameters. You can also
optionally specify the maximum vertical size, in pixels.

iTweak Login module provides very useful tweaks for the standard user login form:

• Lightweight and powerful
• Complements nicely functions of Login Toboggan module (if it is present)
• Works with any theme (that does not already customize user login)
• Customize "Log in" button:
  • select any custom name
• Customize "Username" and "Password":
  • Change labels (if not using LoginToboggan)
  • Add text before username field in login page
• Customize "Create new account":
  • Change link wording
  • Change URL (for example to a custom signup page)
  • Change to a button with any custom name (defaults to "Register")
• Customize "Request new password":
  • Remove link completely
  • Change link wording
  • Change URL (for example to a custom login help page)
  • Change to a button with any custom name (defaults to "Reset Password")
• Perfect for Multilingual websites (locale module required) and Internationalizable (i18n module required) - See Russian example on Screenshot 4
• All custom labels are applied to tabs and buttons on /user/* pages for consistent look
• Adds "can change own password" permission (make sure to enable it for all roles that are allowed to change their own password immediately after module installation).

The labels for the "Title" and "Body" fields (whatever you decide to label them for a given content type) do not get translated in node.module or node.pages.inc. This tiny module takes care of that, passing the labels through t().

According to the developer of the i18n module, a future release of that module will address this issue, making this very simple module unnecessary (see http://drupal.org/node/149349#comment-1181176).

This module extends the views module with a views plugin to make scrollable content with the jquery.scrollable plugin.

Based on http://www.flowplayer.org/tools/scrollable.html .

Responsive Design from before it became fashionable!

This module allows you to organize the layout of specified HTML elements into dynamic columns.
Admins can specify the maximum count of columns and minimum width of one column. Content will be reformatted dynamically depending on size of browser window.

This module is obsolete. Please use Views instead.

This module enables administrators to set a different theme for every node content type.

This is a very simple module that adds a 'title'-attribute to all links in the language selector menu.

Internet Explorer will refuse to load more than 31 linked stylesheets. Unfortunately, the alternative to load styles using @import statements (which Drupal 5 used), has bad performance implications.

The fix for this on production sites is to simply enable the “Optimize CSS files” option on admin/settings/performance. Unfortunately, that option makes developing CSS for themes or modules a true PITA. This module adds a developer-friendly solution to the “Optimize CSS files” feature; it aggregates all stylesheets except for those in the theme or in the selected module.

Skinr's main purpose is to allow the theme to define a set of reusable and modular CSS styles, and to make those styles available in Drupal's UI. Skinr was developed for themers to allow them to tap into the power of Drupal's modularity and apply those same principals to theme development. It does not provide any styles of its own. These styles are defined in the .info file of the theme (or subtheme), by the themer and end up in various places in Drupal's UI, such as:

• Block Configuration
• Node Type (and Comment) Configuration
• Panel Panes
• Views Displays

It also provides a CSS class field, where you can manually add custom classes.