Celebrating 20 years online :)
Web Dev + WordPress + Security

The Power of HTML 5 and CSS 3

[ Electrical Surge ]

Web designers can do some pretty cool stuff with HTML 4 and CSS 2.1. We can structure our documents logically and create information-rich sites without relying on archaic, table-based layouts. We can style our web pages with beauty and detail without resorting to inline <font> and <br> tags. Indeed, our current design methods have taken us far beyond the hellish era of browser wars, proprietary protocols, and those hideous flashing, scrolling, and blinking web pages. Thankfully, those days are over.

As far as we’ve come using HTML 4 and CSS 2.1, however, we can do better. We can refine the structure of our documents and increase their semantic precision. We can sharpen the presentation of our stylesheets and advance their stylistic flexibility. As we continue to push the boundaries of existing languages, HTML 5 and CSS 3 are quickly gaining popularity, revealing their collective power with some exciting new design possibilities.

Goodbye <div> soup, hello semantic markup

In the past, designers wrestled with semantically incorrect table-based layouts. Eventually, thanks to revolutionary thinking from the likes of Jeffrey Zeldman and Eric Meyer, savvy designers embraced more semantically correct layout methods, structuring their pages with <div> elements instead of tables, and using external stylesheets for presentation. Unfortunately, complex designs require significant differentiation of underlying structural elements, which commonly results in the “<div>-soup” syndrome. Perhaps this looks familiar:

<div id="news">
   <div class="section">
      <div class="article">
         <div class="header">
            <h1>Div Soup Demonstration</h1>
            <p>Posted on July 11th, 2009</p>
         <div class="content">
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
         <div class="footer">
            <p>Tags: HMTL, code, demo</p>
      <div class="aside">
         <div class="header">
            <h1>Tangential Information</h1>
         <div class="content">
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
         <div class="footer">
            <p>Tags: HMTL, code, demo</p>

While slightly contrived, this example serves to illustrate the structural redundancy of designing complex layouts with HTML 4 (as well as XHTML 1.1 et al). Fortunately, HTML 5 alleviates <div>-soup syndrome by giving us a new set of structural elements. These new HTML 5 elements replace meaningless <div>s with more semantically accurate definitions, and in doing so provide more “natural” CSS hooks with which to style the document. With HTML 5, our example evolves:

            <h1>Div Soup Demonstration</h1>
            <p>Posted on July 11th, 2009</p>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Tags: HMTL, code, demo</p>
            <h1>Tangential Information</h1>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Lorem ipsum text blah blah blah.</p>
            <p>Tags: HMTL, code, demo</p>

As you can see, HTML 5 enables us to replace our multitude of <div>s with semantically meaningful structural elements. This semantic specificity not only improves the underlying quality and meaningfulness of our web pages, but also enables us to remove many of the class and id attributes that were previously required for targeting our CSS. In fact, CSS 3 makes it possible to eliminate virtually all class and id attributes.

Goodbye class attributes, hello clean markup

When combined with the new semantic elements of HTML 5, CSS 3 provides web designers with god-like powers over their web pages. With the power of HTML 5, we obtain significantly more control over the structure of our documents, and with the power of CSS 3, our control over the presentation of our documents tends toward infinity.

Even without some of the advanced CSS selectors available to us, the new variety of specific HTML 5 elements enable us to apply styles across similar sections without the need for defining class and id attributes. To style our previous <div>-soup example, we would target the multitude of attributes via the following CSS:

div#news    {}
div.section {}
div.article {}
div.header  {}
div.content {}
div.footer  {}
div.aside   {}

On the other hand, to style our HTML 5 example, we may target the various documents regions directly with this CSS:

section {}
article {}
header  {}
footer  {}
aside   {}

This is an improvement, but there are several issues that need addressed. With the <div> example, we target each area specifically through use of class and id attributes. Using this logic allows us to apply styles to each region of the document, either collectively or individually. For example, in the <div> case, .section and .content divisions are easily distinguished; however, in the HTML 5 case, the section element is used for both of these areas and others as well. This is easily resolved by adding specific attribute selectors to the different section elements, but thankfully, we instead may use a few advanced CSS selectors to target the different section elements in obtrusive fashion.

Targeting HTML-5 elements without classes or ids

Rounding out the article, let’s look at some practical examples of targeting HTML-5 elements without classes or ids. There are three types of CSS selectors that will enable us to target and differentiate the elements in our example. They are as follows:

  • The descendant selector [CSS 2.1]: E F
  • The adjacent selector [CSS 2.1]: E + F
  • The child selector [CSS 2.1]: E > F

Let’s have a look at how these selectors enable us to target each of our document sections without the need for classes or ids.

Targeting the outermost <section> element

Due to the incompleteness of our example, we will assume that the outermost <section> element is adjacent to a <nav> element which itself is a direct descendant of the <body> element. In this case, we may target the outermost <section> as follows:

body nav + section {}

Targeting the next <section> element

As the only direct descendant of the outer <section>, the next <section> element may be specifically targeted with the following selector:

section > section {}

Targeting the <article> element

There are several ways to target the <article> element specifically, but the easiest is to use a simple descendant selector:

section section article {}

Targeting the <header>, <section>, and <footer> elements

In our example, each of these three elements exists in two locations: once inside the <article> element and once inside the <aside> element. This distinction makes it easy to target each element individually:

article header {}
article section {}
article footer {}

..or collectively:

section section header {}
section section section {}
section section footer {}

So far, we have managed to eliminate all classes and ids using only CSS 2.1. So why do we even need anything from CSS 3? I’m glad you asked..

Advanced targeting of HTML 5 with CSS 3

While we have managed to target every element in our example using only valid CSS 2.1, there are obviously more complicated situations where the more advanced selective power of CSS 3 is required. Let’s wrap things up with a few specific examples showing how CSS 3 enables us to style any element without extraneous class or id attributes.

Targeting all posts with a unique post ID

WordPress provides us a way of including the ID of each post in the source-code output. This information is generally used for navigational and/or informational purposes, but with CSS 3 we can use these existing yet unique ID attributes as a way to select the posts for styling. Sure, you could always just add a class="post" attribute to every post, but that would defeat the point of this exercise (plus it’s no fun). By using the “substring matching attribute selector,” we can target all posts and their various elements like this:

article[id*=post-] {}           /* target all posts */
article[id*=post-] header h1 {} /* target all post h1 tags */
article[id*=post-] section p {} /* target all post p tags */

Now that’s just sick, and we can do the same thing for numerically identified comments, enabling us to apply targeted styles to associated constructs:

article[id*=comment-] {}           /* target all comments */
article[id*=comment-] header h1 {} /* target all comment h1 tags */
article[id*=comment-] section p {} /* target all comment p tags */

Target any specific section or article

Many sites display numerous of posts and comments. With HTML 5, the markup for these items consists of repetitive series of <section> or <article> elements. To target specific <section> or <article> elements, we turn to the incredible power of the “:nth-child” selector:

section:nth-child(1) {} /* select the first <section> */
article:nth-child(1) {} /* select the first <article> */

section:nth-child(2) {} /* select the second <section> */
article:nth-child(2) {} /* select the second <article> */

In a similar manner, we may also target specific elements in reverse order via the “:nth-last-child” selector:

section:nth-last-child(1) {} /* select the last <section> */
article:nth-last-child(1) {} /* select the last <article> */

section:nth-last-child(2) {} /* select the penultimate <section> */
article:nth-last-child(2) {} /* select the penultimate <article> */

More ways to select specific elements

Another way to select specific instances of HTML-5 elements such as <header>, <section>, and <footer>, is to take advantage of the “:only-of-type” selector. With these HTML-5 elements appearing in multiple locations in the web document, it may be useful to target elements that appear only once within a particular parent element. For example, to select only <section> elements that are the only <section> elements within another <section> element (insane, I know), as in the following markup:

      <section>Target this section</section>
      <section>Target this section</section>
      <section>But not this section</section>
      <section>And not this section</section>

..we could simply use the following selector:

section>section:only-of-type {}

Again, you could always add an id to the target element, but you would lose the increased scalability, maintainablity, and clarity made possible with an absolute separation of structure and presentation.

The take-home message for these examples is that CSS 3 makes it possible to target virtually any HTML-5 element without littering the document with superfluous presentational attributes.

Much more to come

With the inevitable, exponential rise in popularity of both HTML 5 and CSS 3, designers can look forward to many new and exciting possibilities for their web pages, applications, and scripts. Combined, these two emerging languages provide designers with immense power over the structure and presentation of their web documents. In my next article on this topic, we will explore some of the controversial aspects of HTML 5 and also examine some of the finer nuances of CSS 3. Stay tuned!

Note to WordPress users

You can start using HTML 5 right now. To see a live, working example of a WordPress theme built entirely with HTML 5, CSS, and of course PHP, drop by the Digging into WordPress site and visit our newly revamped Theme Clubhouse. There you will find my recently released H5 WordPress Theme Template available for immediate download. And while you’re there, be sure to secure your copy of Digging into WordPress, coming this Fall.

About the Author
Jeff Starr = Web Developer. Security Specialist. WordPress Buff.
Digging Into WordPress: Take your WordPress skills to the next level.

46 responses to “The Power of HTML 5 and CSS 3”

  1. After reading this entry only then I realize the significance of the H5 WordPress Theme you’ve realized, as well as the importance of you highlighting that the theme doesn’t use any classes or ids (except for the classes assigned to the body tag, and you’ve explained it well over at DiW). I’ve heard of the adjacent and child selector before, but I’ve rarely used them, let alone understand how they can be actually applied. I’ve been using the descendent selector most of the time, and this post came at the right time to help me brush up my knowledge of the less known selectors. Looks like it’s time for me to study the CSS Cheat Sheet again :) heheh!

    Thank you so much for explaining how the selectors work! The nth-child and nth-last-child pseudo-classes are very useful too – so far I’m yet to read someone to explain them as in-depth as you did, Jeff. Terrific job you’ve done over here! I wonder how much time and effort you’ve invested in writing this useful entry.

    I’ve read a few jQuery/Prototype tutorials so far on how to target the nth-child or nth-last-child siblings, but I guess as CSS3 support becomes more prevalent, we can relieve ourselves from resorting to javascript to make simple things like this work.

    Speaking of which, IE6 should really just die :D

    Thank you again :) have a great week!

  2. Simon Sigurdhsson 2009/07/20 12:07 am

    Good article, although I would like to point out that <section> is getting kind of mis-used here. The <section> element is supposed to mark up sub-sections of articles, it is not something you’d use to wrap an article. I wrote a post about it (404 link removed) myself some time ago.

    And also, <section> is not just a “semantic <div>”.

  3. This is a very nice article to give an idea on how html5 and css3 will effect all.

  4. This article nicely shows how we can benifit from HTML5 and CSS3 !

  5. Wayne Smallman 2009/07/20 5:11 am

    While I can see the benefits, we’ve gone from division soup to semantic mayhem – there are just too many ways of doing the same thing.

    If someone starts mixing up all of the different methods within the same sheet, their code will be reduced to an indecipherable mess…

  6. Mike Bruns 2009/07/20 5:56 am

    I have to agree with Wayne on this one. The “div-soup” as you call it only gets cumbersome if you let it.

    What is presented here with HTML 5 seems cleaner yes, but it also seems like it would create more headaches as far as singling out various elements to be styled.

    I’ll be sticking with XHTML for a while if this is the future.

  7. Thom Lohman 2009/07/20 5:22 am

    I’m not sure that I’m comfortable with the implication that assigning IDs (less so with classes) to elements blurs the line between content and presentation. Though it’s not a matter of semantics, an “ID”–once assigned–becomes an intrinsic part of establishing an element’s identity (subject to scripted or programmatic changes, of course), but says nothing about how an element and its descendants should be styled or presented. I may be viewing this issue through some lens of opportunistic antiquity, but I rather like assigning IDs (responsibly and in appropriate measure) and not relying completely on hierarchical relationships between elements that may not always be preserved.

    Great post though–definitely excited for HTML5–rather dejected about the demise of XHTML 2, as I’ve preferred its embracing of strictly composed, clean code. Either way, HTML5 is an improvement over the white elephant that HTML 4 has become!

  8. Kenneth Nordahl 2009/07/20 7:11 am

    Isnt it a error in the following?

    section:nth-child(1) {} /* select the first */
    article:nth-child(1) {} /* select the first */

    section:nth-child(2) {} /* select the second */
    article:nth-child(2) {} /* select the second */

    Computers start to count at 0 right? … so the correct code is

    section:nth-child(0) {} /* select the first */
    article:nth-child(0) {} /* select the first */

    section:nth-child(1) {} /* select the second */
    article:nth-child(1) {} /* select the second */

  9. manoj karmocha 2009/07/20 6:18 am

    Great reading you article !
    is this technology started to be implemented globally?
    I am a also a css developer , I am looking forward to implement in my upcoming projects..

  10. Kenneth Nordahl 2009/07/20 8:09 am

    Ok, my comment was mixed up with section:nth-child(2n+1) {} – styling of every 2nd child element of the section.

    Src: http://net.tutsplus.com/tutorials/html-css-techniques/html-5-and-css-3-the-techniques-youll-soon-be-using/

    Under the heading “Zebra-striping the Comments”.

  11. Jeff Starr 2009/07/20 7:38 am

    @Kenneth: According to the W3C:

    The index of the first child of an element is 1


  12. Jason G Backus 2009/07/20 8:47 am

    Big thanks from those of us currently swimming in div soup.

Comments are closed for this post. Something to add? Let me know.
Perishable Press is operated by Jeff Starr, a professional web developer and book author with two decades of experience. Here you will find posts about web development, WordPress, security, and more »
BBQ Pro: The fastest firewall to protect your WordPress.
Crazy that we’re almost halfway thru 2024.
I live right next door to the absolute loudest car in town. And the owner loves to drive it.
8G Firewall now out of beta testing, ready for use on production sites.
It's all about that ad revenue baby.
Note to self: encrypting 500 GB of data on my iMac takes around 8 hours.
Getting back into things after a bit of a break. Currently 7° F outside. Chillz.
Get news, updates, deals & tips via email.
Email kept private. Easy unsubscribe anytime.