I wasn’t really HTML5′s biggest fan. The fact that you can write it however you want made me very worried that it might result in poor coding again (unclosed tags, or mismatched closing tags). But after reading Introducing HTML5 and HTML5 for Web Designers, I realized that what it lacked in rigid coding conventions it made up with semantic elements like
footer to name a few.
If you’re planning on learning more about HTML5 then I suggest that you pick up these two books as it will help you immensely. Funny enough, while I’m reading these books, I suddenly realized how bad I did in coding this site up. I’m currently in the process of re-writing the entire thing while keeping in mind the mobile first philosophy. It’s a little challenging, but that’s how things get more fun, right? (I sure miss IE a little bit.)
Introducing HTML5 by Bruce Lawson and Remy Sharp
Bought Introducing HTML5 (ref) a couple of days after I got my Kindle. The sample file was engaging and I thought it would be great to read about HTML5 in one place. The web is just buzzing with HTML5 news and tips and tricks that just getting up to date is hard to do.
The book uses a conversational tone and it’s probably the biggest reason why I love it. Bruce Lawson and Remy Sharp were able to discuss the difference between seemingly similar elements in a very clear and concise way. The explanations are so easy to understand that I just realized that, unfortunately, the only thing I did right in my markup (in this site) is using
article for my blog posts.
The book is divided into 10 chapters, they discussed how HTML started to structuring text elements and new types of forms, to using
audio tags properly as well as
canvas, how to access and set data storages, offline mode, drag and drop, geolocation and APIs.
I love how in-depth the book is, it gave a lot of examples that you can follow throughout the book, the discussions on which element is which and what for is so succinct. Introduction to HTML5 is a very meaty one, it’s the type of book you’re going to consult over and over again.
I think it’s just a case of it’s me not you here, but the discussion about the APIs just went whoosh over my head. I did try to read it over and over and over but it kept on making me nod to sleep so I just gave up and vowed to pick it up again when I can understand most of it and not look at the words and abbreviations as if they’re just a bunch of gibberish.
HTML5 for Web Designers by Jeremy Keith
The book is neither too short nor too long. It was just the right length to keep you interested while giving you the best blow-by-blow on the new things that HTMl5 has to offer. The book is divided into 6 comprehensible chapters, like in Introducing HTML5, it touched on a brief history of HTML with less focus on the politics behind it.
The book is such a light read, I think I was able to finish through in about a day. Jeremy Keith not only described what the elements are for and the best case scenario for each of them but he also gave a script for backwards compatibility. I really, really love that its tone is conversational, that’s why I also love Web Standards Solutions: The Markup and Style Handbook, Special Edition (ref) by Dan Cederholm. I am such a sucker for these types of books because in my experience, technical books tend to be… well, too technical and boring.
Cons (not so much)
I think I would have liked it if he tackled on canvas, and the APIs in the book no matter how lightly he discussed it. I think I’ll be able to understand it even more instead of me getting so lost on how to make all those things work. He did mention that he won’t touch it in the beginning of the book but still, you can’t help but feel wanting in the end.