Menu Minipanels is a very cool little module that allows you to attach a mini panel to a menu item, which then pops open when you hover the menu item - aka instant mega menu!

Adaptivetheme 7.x-2.x includes a new layout engine that drives both responsive and adaptive layouts using media queries. We've made it super easy to configure layouts for standard desktops and laptops, and tablet and smartphone size screens. This video features Pixture Reloaded, an Adaptivetheme subtheme available for free download on Drupal.org and shows off the layout settings and a brief run down on how it all works.

In short I have re-written the way layouts work in Adaptivetheme to support mobile, tablet and standard screens.

Adaptivetheme 7.x-2.x uses media queries combined with a more flexible approach to setting values for the sidebars, page width, max width (for responsive layouts), and you can customize the media query - all in the theme settings.

I get asked all the time how to add a CSS file to Drupal, its seems like the most rudimentary thing to do in a modern website, however Drupal has more than one way to add CSS files so here's an in depth explanation of the different ways you can add your files and why you might choose a particular method.

The docs team have spotlighted Drupal 7 theme documentation for May, you can read all about it here: http://groups.drupal.org/node/143419

The docs seriously need work so anyone with theming experience who can give a couple of hours some time during May to help out would be fantastic - I know I'll do my best to help improve the docs, so please get involved.

Way back in September 2010 I launched the Design 4 Drupal Core (D4DC) project - the initial goal was to define a better process for adding new themes to Drupal core. This grew out of the Drupal 7 process which was essentially a code race between Bartik and Corolla. It was clear to me this process could be improved. In the commercial world we always select the design first (as opposed to an entire theme), so I started making the argument that any new core theme would have to be selected based on the design - then coded into theme.

This is bound to stir up some debate because in fact you can use aside to markup sidebars, it could be a good fit, but in Drupal core, or in a generic theme (as in one not built specifically for your site) then using aside is wrong and I am going to argue as to why this is so.

HTML5 has a bunch of new form attributes and one of these can neatly add placeholder text to text inputs, such as your search input field. This text will be removed when the search field is focused, so in effect acts like ye ole JS solutions we've all been using for eons.

Browser support for placeholder looks pretty good, I have it working in Opera 11 and FF4. It should be widely supported in all the next generation browsers.

Hooray, we just launched our first three premium Drupal 7 themes - Biz, Vibrant and Magazine.

All our themes use Drupal's color module and have advanced settings for layout, fonts, breadcrumbs, search results, menu bullets and even background "overlay" images.

This debate is going to rear its head in the Drupal community sooner rather than later because right now we're seriously thinking about HTML5 for Drupal 8, and because many new HTML5 themes are springing up.

The issue is that <section> elements must have a heading, that is an <h*> element. If they don't have a heading then technically they're not a section. This is problematic for Drupal blocks because headings are optional, even end users can toggle the display of the block heading.