The first thing you need to do with html5 boilerplate is delete most of it.
You would only go keep all the crap they throw in there if you a) do not know who your customers are and what your target browsers are, b) what your content delivery and hosting platforms are, c) what you actually want on your website, d)what HTML, CSS and JavaScript you will need to achieve that, and e) how to make a fast and efficient website or web application.
Make no mistake, Html5 boilerplate, Modernizr, and other libraries of that ilk get in the way of good web development, rather than enable it.
I'd delete even more than is suggested in that article. Far too much in that reset CSS that you will never need.
There. And I didn't resort to personal insults either.
I suggest you do some reading. Might as well start here:
http://csswizardry.com/2011/01/the-real-html5-boilerplate/
The first thing you need to do with html5 boilerplate is delete most of it.
You would only go keep all the crap they throw in there if you a) do not know who your customers are and what your target browsers are, b) what your content delivery and hosting platforms are, c) what you actually want on your website, d)what HTML, CSS and JavaScript you will need to achieve that, and e) how to make a fast and efficient website or web application.
Make no mistake, Html5 boilerplate, Modernizr, and other libraries of that ilk get in the way of good web development, rather than enable it.
I'd delete even more than is suggested in that article. Far too much in that reset CSS that you will never need.
There. And I didn't resort to personal insults either.