themes

The purpose of this theme is to serve as an example of all the features a theme can have. Pistachio is not intended for actual use on a site, and definitely should not be used on a production site.

The purpose of this theme is to serve as an example of all the features a theme can have. Pistachio is not intended for actual use on a site, and definitely should not be used on a production site.

The purpose of this theme is to serve as an example of all the features a theme can have. Pistachio is not intended for actual use on a site, and definitely should not be used on a production site.

The purpose of this theme is to serve as an example of all the features a theme can have. Pistachio is not intended for actual use on a site, and definitely should not be used on a production site.

Seven theme is a special case that has to cover a lot of ground: It has to be completely accessible Mobile friendly Provide consistency across 20.000 modules Stand the test of time – as it is often the main way people interact with Drupal and one of the main ways people come to understand the Drupal brand. This is a proposal, so we hope to receive loads of feedback.

By default making a sub-theme of Bartik in Drupal does not bring across the color wheel module, but with a slightly modified sub-theme set up, this can be enabled. The trick is to make a css directory and put your custom css in there and also copy across the existing bartik color css files.

By default making a sub-theme of Bartik in Drupal does not bring across the color wheel module, but with a slightly modified sub-theme set up, this can be enabled. The trick is to make a css directory and put your custom css in there and also copy across the existing bartik color css files.

In adddition to the changes made to the D8 version, this version will also include the following features:

HTML5 markup
WAI-ARIA accessibility roles added to primary elements
Html5shiv, Respond.js, Selectivizr.js for IE versions 7 & 8

front-end performance is more critical then back-end performance. Front-end performance is also a critical priority for Zen. That’s why Zen 5’s markup and CSS footprint is so small. After turning on Sass production-mode compilation, the total CSS is only 14k; this includes the layout, vertical rhythm support, print styles, all the appropriate vender prefixes (like -o and -khtml), CSS3-prettified tab styling and the 3 menu images that are included via Data URIs into the CSS. Zen includes no images and only 2 JavaScripts (which are only loaded conditionally by IE8 and lower,

Front-end performance is also a critical priority for Zen. That’s why Zen 5’s markup and CSS footprint is so small. After turning on Sass production-mode compilation, the total CSS is only 14k; this includes the layout, vertical rhythm support, print styles, all the appropriate vender prefixes (like -o and -khtml), CSS3-prettified tab styling and the 3 menu images that are included via Data URIs into the CSS. Zen includes no images and only 2 JavaScripts (which are only loaded conditionally by IE8 and lower, but also minified and pre-aggregated together).