A New Book on HTML5 and CSS3

The book is called HTML5 & CSS3 for the Real World and was officially launched on SitePoint this morning (North American time).
Two other authors took part in this exciting new project: Estelle Weyl — who probably doesn’t need much of an introduction if you’re familiar with many conference speakers in the web standards world — and Alexis Goldstein, a well-rounded programmer from Brooklyn.
If you’re starting to incorporate some HTML5 and CSS3 into your pages, then you’ve probably also looked into the possibility of
I have a wide monitor and I like my windows to be maximised (I’m on Windows 7). I also like when Chrome is maximised, because I usually have about 7,623 tabs open at any given time, so the bigger the window, the better.
With all the excitement over the flashy new stuff in CSS3 (like transitions, transforms, and keyframe animations), some other properties may get pushed into the … well… background.
Baseball season is in full swing in North America and I’ve noticed some nice changes to the design of the
This is not going to be an extensive post, but just something to serve as a quick reference, along with some interesting points from
After years of developing CSS layouts and reading web design blogs and CSS books, I still can’t believe I come across things that I don’t know about super-common CSS properties.
This is not going to be a long article, but just a quick note about something that all front-end developers should be paying attention to.
It would seem that with the introduction of HTML5’s semantic elements, styling those new elements should be an easier task. But as I’ve started to use HTML5 more, I’ve realized that it takes quite a bit of forethought to create maintainable CSS that targets the new semantic elements in a future-proof way.
I’ll be the first to admit that I haven’t given this too much thought, so I admit there could be some drawbacks I haven’t considered, but I thought I’d throw the idea out there and see what my readers think.