CSS

Omega Theme: Withering Heights?

Tue, 07/05/2011 - 18:51 -- James Sinkiewicz

Screen Shot

Force Equal Height For All Child Elements

The first time I saw the setting in the configuration section of a Zone to 'Force equal height for all child elements.', I thought to myself that this would be a pretty useful selection box. I mean, why wouldn't anyone want all the 'blocks' in a zone to be the same height? It would make the page look professional and polished. So, without hesitation, I checked the box, reloaded the page, and waited with anticipation to see my Heathcliff and Catherine blocks together again with equal heights (shameless play on Wuthering Heights).

Omega StarterKit CSS Files

Thu, 06/30/2011 - 11:57 -- James Sinkiewicz

Screen Shot

If you've watched any of the Omega Theme videos available on the Internet (see Jake Strawn (aka himerus) Introduction), you will hear the Omega Theme described as being built from 'mobile to desktop", instead of from desktop down to mobile. The basic idea is that the 'default style' of a website should be one that looks good on mobile devices and that stylesheets should change as the browser window's size is changed or pages are displayed on different sized devices. There are so many stylesheets associated with the Omega theme that I was easily overwhelmed and confused. This article attempts to describe how some of the various CSS stylesheets that are involved in that process are configured.

Starterkit CSS Files

After you've create a custom theme from the Omega base theme using one of the starterkit folders provided with the theme, you will find 5 files in your custom_theme/css folder. Most of these files are named after the starterkit you chose. The list below are those files included in the omega-html5 starterkit as of this writing:

Context and Omega: User Zone

Thu, 06/16/2011 - 07:32 -- James Sinkiewicz

Screen ShotHaving made the commitment to use the Omega theme and Delta module, of course the Context module is the place to start when creating a new website. I've come to think of Context as a replacement for the Drupal Core Blocks system. Previously, when I wanted a block to show up on one page, but not one or two others, I had to create settings for the block's visibility to "Show block on specific pages ~ All pages except those listed" and then list the individual pages that I did not want the block to appear. If there was some kind of taxonomy or URL pattern that could be discerned, then I could use that, but mostly it came down to listing the individual page exceptions. The biggest problem with that was when you created a new page, you might forget to add that page to the list of exceptions.

Subscribe to RSS - CSS