THEME FIND

This is a port of the Wordpress theme by the same name. The theme uses the Blueprint CSS Framework which provides "an easy-to-use grid, sensible typography, and even a stylesheet for printing. "

The original NeeWee is released by Mattias Hising under the GNU General Public License v2.

This Drupal port strives to maintain the simple cleanliness of the original while integrating basic Drupal functionality with the outcome being a good-looking and useable website that does not look like a Drupal website.

This theme is still a work in progress with some rough edges. Please submit issues and hopefully we can update its status to "somewhat tarnished" :-)

The Paris sprint will happen at http://www.rentals.chsparis.com/mnt/mnt.htm. Joeri is the local project manager, Gabor is the technical lead, and Dries is the lead organizer.

Eclipse, with the newly released PDT 2.0, is a very capable Drupal IDE. With code completion, automatic documentation lookups, and integrated debugging, Eclipse is very good for anyone who spends time doing Drupal code.

One issue I've run into with Eclipse when working on contributed modules is that the modules themselves aren't located within a Drupal installation. I found myself resorting to external programs or the command line to copy my changes to my development site or to my local development copy. Using Eclipse's External Tools, it's possible to deploy changes with a single click, greatly reducing the time to test modified code.

This is a very clean and professional looking "Web 2.0-style" theme for Drupal 6 and upward.

Some of its features include;

• Supports site name, slogan, mission, comment user pictures, search box, and primary and secondary links.
• Dynamic multiple column layouts and allows for easy resizing of the main content regions.
• Includes an attractive maintenance/site off-line template.
• CSS based (no tables) design and valid XHTML 1.0 Strict / CSS 2.1.
• Integration of Suckerfish drop-down menu into primary links.
• Small file sizes to achieve a light-weight and fast-loading website.
• Several configurable styles for the primary navigation and footer.
• Tabs based on the sliding doors technique with hover-over effects.
• Support for several popular modules including I18N, Image Assist, Digg This, Taxonomy, etc.

This theme may be used and modified as long as the links in the footer remain unmodified and visible.

A demo of the theme is visible on Vitzo.com. This website uses the suckerfish primary navigation style. The other style looks more like that of Oondi.

This module allows certain clients from using different themes, based on a defined string in the User Agent. Based on that string, a theme will be assigned to that particular kiosk. The theme can be shared for a group of kiosks, or restricted for an individual kiosk.

Drupal's normal mode page caching is supported.

Comparison with Kiosk module

The kiosk module has similar high level goals, but different design and implementation. Here are the important differences:

• Kiosk uses the IP address or a cookie to place a certain client in kiosk mode. Kiosk theme uses a certain string in the browser's user agent to assign a predefined theme.
• Kiosk provides a theme variable that has to be checked within the theme to enabled/disabled certain features (e.g. a navigation menu). Kiosk theme enables a predefined theme that is different and separate from the main theme of the site for each kiosk or group of kiosks.
• Both modules use a database prefix trick to do page caching and are incompatible with aggressive caching.

read more

The editing form of a node is themed using theme('node_form'), which is implemented by the theme_node_form() function in Drupal core's node module and can be overridden by adding a <theme_name>_node_form() function in the theme's template.php file. However, this is less convenient and less powerful than taking advantage of Drupal's templating system. Why not be able to override by placing a node-form.tpl.php file in the theme's folder and allow modules to use preprocess functions for customization? This module allows exactly that.

This is a simple module that adds a "node-content" theme hook to Drupal for theming the $node->content array. For example, with this module enabled, you can create a "node-content--page.tpl.php" file in your theme's folder, giving you templating control of the "Page" content type. This can be used for any content type, but the use-case I expect it to be most useful for is in having greater theming control of content types that use CCK fields.

There's another module, contemplate, that solves a similar use-case. That module, however, is more geared to providing template control via the CMS interface, whereas this module is more geared to providing it via the normal theming system. Pick the one appropriate to the way you like to work, or mix and match.

Instead of this module, you can take the approach of using "node-<type>.tpl.php" files, as described on http://drupal.org/node/62462. However, then you end up duplicating all of the generic markup that deals with the node title, links, terms, and publish status, that you don't necessarily need to have customized per type. If you want to customize all that generic stuff per type, use those tpl files. But if you only need to customize the node's type-specific content, then this module might be useful for you.

This module depends on:

read more

Blue Citron actually provides two themes, one fixed width and one fluid width. I always build themes like this so that you can use the fluid width version for the admin areas of the site.

It also changes the CSS for the Jquerymenu module a little to make the theme match (if you happen to be using that module).

I can be contacted for customizations of this theme or for other projects through my contact form or at www.PixelClever.com.

PS: This theme is for Drupal 6 only and will not be backported.

CWS was designed to try and fill the requirement for an accessible Drupal theme.

Andre Griffin's "Framework" theme was chosen as the backbone, but a number of modifications have been made to satisfy WCAG requirements.

* CWS retains the fixed width layout with autoresizing center column if either left or right sidebars are disabled.
* All fonts are stated in relative sizes as opposed to fixed font sizes.
* Colour contrast of the elements pass automated testing.

A demo of the theme can be found at http://www.christianwebsolutions.co.uk/