
The HTML5 spec is 900 pages and hard to read. HTML5 for Web Designers is 85 pages and fun to read. Easy choice. HTML5 is the longest HTML specification ever written. It is also the most powerful, and in some ways, the most confusing. What do accessible, content-focused standards-based web designers and front-end developers need to know? And how can we harness the power of HTML5 in today’s browsers? 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.
Think about this: I can see from the linked page that you understand how adding type="password" to an input makes some consumers, like various web browsers, treat that field differently. There's a lot of stuff like that in HTML.
If you want a short intro that also explains some of the "why" behind various aspects of HTML5, read this: http://www.abookapart.com/products/html5-for-web-designers
The HTML5 spec also has a lot of info ( http://www.w3.org/TR/html5/grouping-content.html#the-div-ele... ). For example:
> Authors are strongly encouraged to view the div element as an element of last resort, for when no other element is suitable. Use of more appropriate elements instead of the div element leads to better accessibility for readers and easier maintainability for authors.
CSS Mastery: http://www.cssmastery.com/
Bulletproof Web Design http://astore.amazon.com/simplebits-20/detail/0321509021
Web Standards Solutions: The Markup and Style Handbook http://astore.amazon.com/simplebits-20/detail/1430219203
Handcrafted CSS http://handcraftedcss.com/
It would be worth to check out some about HTML5:
Brief but good introduction: http://books.alistapart.com/products/html5-for-web-designers
Also: http://introducinghtml5.com/ and http://diveintohtml5.org/
The HTML5 spec is current, uses hyperlinks and free. Easy choice.
Instead I was greeted with this quote in the book:
The [JavaScript] APIs in HTML5 are very powerful. They are also completely over my
head. I’ll leave it to developers smarter than me to write about them. The APIs
deserve their own separate book.
Fair enough. Those are rather technical subjects and this is an introductory book. I can live with that.More than this being an introductory book, it's a book for designers. The target audience is neatly contained in the title of the book. This means that developers aren't going to get everything they might want out of this book. As he mentions in the article, the term "HTML5" has become an abbreviated moniker for a fairly large set of new-ish web technologies and standards. I'd expect a book entitled HTML5 for Web Designers to read more like CSS3 for Web Designers.
