Theme development

This is a special interest group dedicated to improving and expanding the Drupal theme system including theme functions and templates, CSS, markup, and how contrib modules add in their functions, CSS, and markup.

for example, we'll take stock of the location and number of CSS files and discuss if the architecture can be improved through emerging frameworks like Object Oriented CSS.

We will consider the questions "What do themers need from Core in terms of CSS? Module developers? SEO specialists?" and "What's new in CSS? What does Drupal support? What's the roadmap for CSS support?"

Displaying fields in tpl files, like the node.tpl.php files, is a common desire to designers/themers. After conversations in IRC, at drupalcon, and in the parking lots of the Internet the common thought is that you need to make calls to something like $node->content['field_FOO']['#XXX']; to get to the information.

I've recently learned that there is an easier way to get to it. According to yched, on of the gurus of CCK and fields, you can use $FIELD_NAME_rendered in your .tpl files where fields are attached. This is true in Drupal 6 CCK and Drupal 7 fields.

I'm looking for someone that has a theme for this site, we would like http://www.fantabook.org something fantasy because the theme of the characters are cartoons and manga. those interested and contact me in private.

The Acquia Marina theme uses icons in blocks, which presented an interesting challenge for contributing on drupal.org, since all files must be GPL licensed (PS. the PSD files for Marina are now available for download in our group). Creative Commons licenses don't cut it, which tends to be what icon designers go with when they decide to make free icons available.

Phases

South Central Media is seeking 8-10 theme developers to work approximately 15-25 projects a month starting the first half of April. If you are an experienced themer or even just starting out as a themer and you are interested in doing low complexity theme implementations from fully comped PSD files, please contact me immediately!

At Drupalcon 2009 in Washington, the Drupal design community were asked to become active participants in contributing feedback to the Drupal project.

mfer was kind enough to give members of the Design for Drupal (D4D) Group a tour of how we could provide feedback through the Issue Queue. As a matter of fact, we were shown a version of the issue queue in which any project could be flagged as "needs design review".

I think these attempts have failed due to lack of funding, support and clear organization. I want to get the ball rolling on this. Please reply with your ideas and comments. Here are my ideas I'm tossing around.

I posted a preliminary patch over issue queue http://drupal.org/node/395116 to stir a discussion whenever we need CSS reset in core and how core CSS setup -- file structure, rulesets etc -- should look like in D7. reset.css proposal is could be the first step in having decent CSS framework in core -- or if that is not gonna happen, just enforce some sensible CSS practices.

Do you think color.module should be apart of core? If so, should it be upgraded from its current state?

Do you find the color.module is tedious or complex? Do you find it beneficial to simple themes? To advanced ones?

Also, for D7, I'm proposing the idea of an open styling system in addition or replacement to color.module. This styling system would allow themers to create prerendered skins and also accept skins from the files layer (meaning it can use color.module schemes).

This workshop shows how you'll get the most out of display options like blocks and pages, plus how to theme your views with PHP templates. Take away masterful tips like how to embed views (meaning views within views), and some magical views that only a developer can love.

I'm just talking about breadcrumbs up: the simple, unostentatious way primary and secondary menus are presented. Yet the color contrast between the two and the use of tabs to highlight the active menu improves usability.

Also a lot of stuff is packed into the header and yet content area starts from relatively high up -- again a plus for usability on small screen.