Theme related

The Style Override module allows administrators to define CSS selectors whose properties can be manipulated based on admin defined rules. The style manipulation is done though a form on the pages to which the rules apply. JavaScript allows the user to see the changes made (for example to font size or font family) before saving them.

Vertical Tabs module allows you to output form (in our case, node form) fieldsets as vertical tabs. Vertical Tabs Default Tab advances this behaviour, allowing you to move remaining top level node form elements (such as title and body) into default vertical tab, leaving only buttons below. This reduces height of node forms, greatly improving usability for complex content types with lots of fields/fieldgroups.
Contains code from #357300: Place all top level form elements into a default vertical tab group.

Custom Node Template allows one to specify different node templates to be used on a node by node basis.

While there are many options for customizing the display of pages, fewer options exist for customizing the display of nodes. There are many instances in which customizing the display of specific nodes might be useful, and this module provides a simple and efficient way to achieve this.

Using This Module vs. Other Solutions

If you are looking for a way to customize the display of all nodes within a content type this module would probably not be useful. While you can specify a node template to be used by default for a content type using this module, it only applies to nodes you create in the future. There are better solutions for customizing the display of content types - probably the best way is to just do this through your theme. You may also find some other helper modules to be useful. One of the main reasons for using this module would be to customize or override the display of specific nodes differently from the default display of those nodes. Please see the module's handbook page for additional information.

Please see the Custom Node Template Handbook page for additional information and use cases to help you decide if you should use this module/.

How do I Use This Module?

For users with appropriate permissions, a list of all node templates available in a theme are presented when creating or editing a node. Any node template can be selected to be used to display a particular node. Specific node templates can also be assigned to content types as a default. If a node template is not selected for a content type and specific node, then appropriate node template will be used by a theme as it normally would (per existing node template suggestions).

Firebug for Drupal themeing. See the screenshot and screencast. Note that this module injects markers into the DOM to do its magic. This may cause some themes to behave erratically and less capable browsers may make it worse (especially IE)/. Enable it when needed, and disable it afterwards. There is a handy link in the devel block to do just this.

For Drupal 6, this module was part of the Devel project. For Drupal 7, it is its own project, but relies on the Devel module as a dependency.

Block tab module allows you to display blocks in a region as tabbed contents (1 block content is visible at a time). Block titles are tabs, and block contents are the content.

Installation:

• Enable block_tab module
• Visit the admin setting page to set, which regions should be tabbified: /admin/settings/block_tab

I developed this module at Pronovix, contact us for Drupal consulting or development jobs: http://pronovix.com

The xCSS Framework, by Anton Pawlik, bases on CSS and empowers a straightforward and object-oriented workflow when developing complex style cascades. Using xCSS means a dramatic cut down to your development time by: having a intuitive overview of the overall CSS structure, using variables, re-using existing style cascades and many other handy features. The Drupal module processes all .xcss files that were added to the page via drupal_add_css().

Features

• Variables
• Nesting child objects
• Extending objects
• Math operations
• Comments