Get $500+ of the best After Effects files, video templates and music for only $20!
HTML5 for Web Designers: Book Review

HTML5 for Web Designers: Book Review

HTML5 is all the buzz right now: some people think you need to wait until it’s “complete” to use it, while others are pushing the envelope and using what the browsers are supporting right now. If you’re not following the HTML5 hype and aren’t familiar with what’s so exciting, today’s book review will give you a great source to turn to: “HTML5 for Web Designers.


What’s It About?

It should be obvious what this book is about: HTML5. However, that’s a broad, tangential topic. More specifically, HTML5 for Web Designers is supposed to be a super-condensed, easy-reading version of the HTML5 spec, with a huge scoop of practicality stirred in. I’ve included a few quotes in this review so you can get an idea of what it’s all about.


Who Wrote It?

Jeremy Keith

HTML5 for Web Designers was penned (well, probably typed) by the brilliant Jeremy Keith. If you’re not familiar with Jeremy Keith, you’ve been missing a lot on the web. He’s an Irish web developer, the technical director at Clearleft, a web development firm in Brighton, England. He’s done a lot of work with Microfomats; for more by Jeremy, you should really check out his blog, Adactio. Mr. Keith was interviewed by Dan Benjamin and Jeffrey Zeldman on the Big Web Show, talking about why the book was written, why Jeremy was chosen to write it, and a lot of other fun stuff.

Listening to that podcast, you’ll agree that Jeremy Keith was definitely the right guy to write this book. If you’ve never read anything by Jeremy Keith before, then a small piece of your web-developer self has yet to be born. Nothing in this book could be more practically explained. The website says it well:

In this brilliant and entertaining user’s guide, Jeremy Keith cuts to the chase, with crisp, clear, practical examples, and his patented twinkle and charm.

You have to love all the fun quips Mr. Keith sprinkled in, from the subtle “an array of programmers” to the more obvious “If you ever use the autoplay attribute in this way, I will hunt you down.”


What’s In The Book?

The Pages of HTML5 for Web Designers

The table of contents shows what exactly you’ll read in this book:

  1. A Brief History of Markup
  2. The Design of HTML5
  3. Rich Media
  4. Web Forms 2.0
  5. Semantics
  6. Using HTML5 Today

Chapter 1: A Brief History of Markup

You might think such a concise book wouldn’t have room for a chapter on the venerable past of HTML . . . but you couldn’t be farther from the truth. In the very first chapter, Jeremy Keith takes you back to the beginning. He clearly explains the path from HTML 2.0 (there never was a version 1) right up to HTML5, visiting famous stops such as HTML 4, XHTML 1, and XHTML 2. He gives a great explanation of why it’s not reasonable to wait for full HTML5 support before using it.

After HTML 4.01, the next revision to the language was called XHTML 1.0. The X stood for “eXtreme” and web developers were required to cross their arms in an X shape when speaking the letter. No, not really. The X stood for “eXtensible” and arm crossing was entirely optional.


Chapter 2: The Design of HTML5

Before diving into too much nitty-gritty, Keith expains some of the philosophies behind HTML5. Among other things, he explains why the new doctype makes sense (and why doctypes are really irrelevant), what’s been removed since HTML4, and how some elements have changed their identities. One of the most interesting parts of this chapter is his explanation of why there are no longer any deprecated elements, only obsolete ones. And don’t miss the section on the new JavaScript API; I won’t spoil it, but I’ll tell you this: fun, fun, fun.

With HTML5, anything goes. Uppercase, lowercase, quoted, unquoted, self-closing or not; it’s entirely up to you.


Chapter 3: Rich Media

I think we’d all agree that the new media offerings in HTML5 are some of the most exciting additions . . . and some of the most controversial. If any of that controversy is caused by a lack of understanding, this chapter will make it all clear. Jeremy very clearly explains all you’d care to know about the canvas, audio, and video tags. He’ll steer your through the murky waters of patchy support and poor accessibility and show you how to use these features successfully.

Fortunately, there’s a way to use the audio element without having to make a Sophie’s Choice between file formats. Instead of using the src attribute in the opening <audio> tag, you can specify multiple file formats using the source element instead.


Chapter 4: Web Forms 2.0

This chapter is about one of the biggest parts of HTML5: forms. Usually, forms are a rather boring topic: not so in this book. Jeremy will take you through each one of the attributes and types of input, as well as teach you how to check for a browser’s support of these new features. You’ll be enlightened to read about why HTML5 includes things like native form validation, and whether or not you should style the new UI elements (Well, you can’t, but he answer the question “Should you want to?”).

I can see why the autofocus attribute has been added to HTML5—it’s paving a cowpath—but I worry about the usability of this pattern, be it scripted or native. This feature could be helpful, but it could just as easily be infuriating. Please think long and hard before implementing this pattern.


Chapter 5: Semantics

This is probably my favourite chapter; to start out, Mr. Keith discusses the issues behind the extensibility of HTML: should you be able to create your own tags, like in XML? Are there other ways to bring meaning to elements? He goes on from there to introduce several of the new elements that HTML5 brings to the table, and shows you how to use them correctly.

Before reading this book, I was somewhat confused about the roles of the new structural elements—things like section and article. Well, colour me enlightened; Jeremy Keith’s explanation will make it all clear. If you really want to challenge yourself, read his explanation of HTML5′s outline algorithm.

Back in 2005, Google did some research to find out what kind of low-hanging fruit could be found on the cowpaths of the web.
A parser looked at over a billion web pages and tabulated the most common class names. The results were unsurprising. Class names such as “header,” “footer,” and “nav” were prevalent. These emergent semantics map nicely to some of the new structural elements introduced in HTML5.


Chapter 6: Using HTML5 Today

It’s nice to know all the theories and specs, but can we really use it? today? As you’ll see, the short answer is “yes”; the long answer is, well, you’ll have to read the book. What’s supported? What’s can you use now? What workarounds are available? It’s all in here, and you’ll be up and running in no time.

I hope that this little sashay ’round HTML5 has encouraged you to start exploring this very exciting technology. I also hope that you will bring the fruits of your exploration back to the WHATWG.


The Summary

It’s amazing how much is actually covered on these subjects in only 85 pages. You’ll learn everything from the history of HTML to how to correctly use the <b> and <i> tags (eh? yes, their back in HTML5). If you want to “try before you buy,” you can check out the first chapter at A List Apart.

Is there anything I’d change in this book? I can’t find anything to complain about; both the publishers and the author are individuals known for their amazing quality of work, and HTML5 for Web Designers is just one more testament to their skill.


Who’s the Book For?

If you’re a web developer, you’ll appreciate this book’s practical knowledge and solid explanations of why things are the way they are. If you’re primarily an experience designer, this book will give you a good grip on using HTML5 semantically and accessibly. If you’re interested in the history of HTML, that’s here. And if you just want a small but elegant book for your shelf, look no further.

In sum, if Nettuts+ is one of your regular web stops, you absolutely must buy HTML5 for Web Designers.

Or, what if you’ve already bought it . . . and read it. If that’s the case, how’s my analysis? Is there anything about the book that you would change?

HTML is the most important tool a web designer can wield. Without markup, the web wouldn’t exist. I find it remarkable and wonderful that anybody can contribute to the evolution of this most vital of technologies.

Add Comment

Discussion 44 Comments

  1. Dan says:

    I just finished reading this book. It was a very informative, yet quick and easy read. I enjoyed it!

  2. Chris says:

    I tried to order this book even though I am not a designer. I am a Front-End guy mostly but trying to get into doing the back-end stuff as well. In any case, they said they didn’t have an e-book yet. So when they get an e-book i’ll buy it. I don’t have to be a dead tree person any longer thanks to Amazon and Apple so I won’t.

  3. w1sh says:

    I’m not upset about all the HTML5 stuff lately, but I’m curious why such a push for it? Are you thinking that if more designers/developers embrace it, that browsers will quickly start to adopt it?

    • John says:

      People are just excited about it. It offers some great new features we use to have to hack. Like the placeholder in a form field. With HTML5 it works without a JS library, and extra code.

      Browsers makers will never listen to designers. IE6 will be around until at least 2014 (when Microsoft will stop supporting it … god I wish they would force an update), But even still IE7, and IE8 will probably be around just as long.

    • Some of the HTML5 and CSS3 features are simply time savers for developers. I’m also assuming it will be more efficient for a browser to implement certain UI animations as opposed to having JavaScript do the leg work.

    • TheAL says:

      Just because it’s the next big thing. It offers a lot of very nice features (as does CSS3) that have been desired for a long time. It’s arguable more semantic and easier to do many standard page elements with specialized tags, making quick page building easier (i.e. header/footer). It’s great to learn it now, experiment with it now, and get familiar with it now. I wouldn’t suggest heavily using it now, advertising it to clients, or converting to it entirely…not yet.

  4. John says:

    “With HTML5, anything goes. Uppercase, lowercase, quoted, unquoted, self-closing or not; it’s entirely up to you.”

    Yay, we get to go back to sloppy coding practices and near impossible to maintain code. I hope he follows that with creating a standard and sticking with it. I learned HTML back in the 2 days, and there was some seriously messed up code.

    Great review, I will probably pick it up, been reading Introducing HTML5 (Voices That Matter). Would be a nice comparison to look at both

    • TheAL says:

      This is one thing about HTML5 that weirds me out. I’m also confused about how HTML5 and XHTML are going to continue to be viewed as being essentially two different things. Are all XHTML practices permissible with HTML5 [meaning, is (x)HTML5 the best way to go]?

      • Davidd says:

        Yes, both HTML and XHTML syntaxes are valid and will validate, as would a mixture of both. As of yet there is no tool for checking specifically against your preferred syntax, but it will come. So, stick with what you prefer. For me, it’s XHTML all the way. Plus, every publishing system I currently use outputs XHTML.

        If by XHTML you mean XHTML2, that project has been axed and is best forgotten.

  5. I know they say, “never judge a book by its cover” but from a developer’s designers standpoint this just has “BUY ME!” written all over it. I think your review covered on all the important points. I have yet to buy any of the HTML5 books. I was debating whether I should get this one or “HTML5: Up and Running” by O’Reilly. When the time comes I think I’ll go with this one first.

  6. Thanks for the review, I am definitely gonna buy it!

  7. Willson says:

    I think I’ll pick up this book, looks like a good read and seems informative. For $18 I really don’t see a down side. Ps. the cover is gorgeous.

  8. Giuliano says:

    Brilliant little book. Very easy to read.

  9. Jeremy Keith says:

    Thank you for the kind words and complimentary review. Glad you liked it.

  10. Randy says:

    Great review! Can you guys review books every week? So many books out there and so expensive after realizing you bought a poorly written book! I’d love to hear it from Nettuts.

  11. Anton says:

    Finished this book a week ago. Being a front end developer, and not a very experienced one I might add, this book was incredibly easy to follow. A must-buy for anyone interested in HTML5!

  12. Ika says:

    Is it free ? If not can you tell me where to buy this book

  13. Michael says:

    I visited Adactio, the blog of Jeremy Keith and choosed the hi-tech theme. I can’t believe this guy is writing books about web development. He is really a web developer…?

  14. Ric Day says:

    Excellent overview of some key elements. Tightly written with a nice sense of humor. Strongly recommended. If future books in this new line are as good, I can see becoming a regular customer.

  15. Maurice says:

    Great intro into HTML5, with nice background. Even as a holiday read it’s very relaxing. Loved the little nerdy jokes.

  16. Brilliant book, well worth reading – even knowing most of the ‘useable’ parts of the spec already.

  17. Jauhari says:

    I hope some where there are some Giveaway for this books ;)

  18. Kevin says:

    I think I’ll pick up this book, looks like a good read and seems informative.

  19. Eddy says:

    No giveaway? ;(

  20. Shane says:

    Jeremy Keith is a good writer. The book’s nice and all, but at $27 (for me in the UK), it is simply TOO expensive for what it delivers.

  21. Yep. definitely buying it … thanks!

  22. Mao says:

    Hi
    am Newbie does this ebook teach me the HTML language from the beginning ?

  23. Ya* says:

    Nice ebook.
    thanks for this review.

  24. I got the book when you posted this article 3 days ago. After reading a few pages, I’d like to suggest it to new generations of web designers like me; it is really easy to read and learn.

  25. Buzzness says:

    Wow, I gotta get this book…

  26. very timely… i had just ordered the book this morning and saw this review by chance just now. very encouraging!

  27. zeldman says:

    Thank you for the thoughtful review. Glad you enjoyed HTML5 For Web Designers. Up next: CSS3 For Web Designers, by Dan (simplebits) Cederholm.

  28. Just ordered and excited.

  29. Dewpro says:

    I was waiting for a book on HTML 5. I think my journey is over.

  30. Matthew says:

    nice! … i like it :)

  31. It’s the very thing i want to catch. Thanks!

  32. iphone spy says:

    Nice reviews. I am going or order one thanks for sharing the resource link.

Add a Comment

To add a code snippet to your comment, please wrap your code like so: <pre name="code" class="html">YOUR CODE</pre>. You can replace the class name with "js," "css," "sql," or "php." If there are any "<" or ">" within your code, please search and replace them with: &lt; and &gt; respectively.