Re:HTML5 Boilerplate - A rock-solid default template for HTML5
by weehuy on Monday March 21, 2011 @02:07PM
(#2350871)
One of the best things about this (and other irish & co. projects)are the explanations and docs. This team always makes reading and understanding what's going on behind the scenes entertaining. It's immensely valuable to a relative newbie like myself.
Re:HTML5 Boilerplate - A rock-solid default template for HTML5
by nkassis on Monday March 21, 2011 @01:51PM
(#2350786)
Yeah, that's a great addition, I'll have to start using it. I'm manually replacing the script tags in my code between deployment because I want to keep all the files separate for debugging and then minify after. It's a pain.
Re:HTML5 Boilerplate - A rock-solid default template for HTML5
by twir on Monday March 21, 2011 @02:06PM
(#2350869)
This looks neat, but being a DIY kind of dude, I'm not sure what this is for. I'm probably missing something--I think I know "what" it is, just not "why". Can anyone give me a brief rundown?
Re:HTML5 Boilerplate - A rock-solid default template for HTML5
by nimbupani on Monday March 21, 2011 @02:12PM
(#2350894)
All of us involved in the project are pretty much "DIY" kind-of people :)
What we hope people do is to read through the source to see why we made the choices for defaults and pick and choose what they like and keep using them.
There are lots of defaults that were eye-opening to me that were suggested by the scores of contributors to the project.
Re:HTML5 Boilerplate - A rock-solid default template for HTML5
by nimbupani on Monday March 21, 2011 @03:06PM
(#2351108)
That is a goal yes, but these are the defaults that work for us, and we hope they work for everyone else (and we do look for suggestions to improve these), but if it does not work for you, we actively advocate choosing the defaults that do.
The reasons for each of the choices we made is all within the comments of the source file, so it is easier to choose what to keep and what to change.
Re:HTML5 Boilerplate - A rock-solid default template for HTML5
by axelav on Monday March 21, 2011 @03:15PM
(#2351133)
I've been using & following the development of this boilerplate since its release & have only continued to be impressed. Thanks for making such a helpful & useful tool.
Re:HTML5 Boilerplate - A rock-solid default template for HTML5
by nvictor on Tuesday March 22, 2011 @07:32AM
(#2353868)
went to the website. got confused by the design. came back to yn to see what's other people like me are saying. they say the like it. going back to get second opinion...
This means everyone's code that does `document.getElementsByTagName('head')[0]` will fail in some cases. Because that is rather risky, we decided to retain these optional elements..
The closing tags for </body> and </html> however...
* A custom builder to customize your download
* An Ant Build Script that handles all the optimization to make YSlow and PageSpeed happy.
* Rich documentation: http://html5boilerplate.com/docs
* Lots of videos (2 new) on Getting Started and familiarizing with the Build Script
* Default webserver configurations optimized for perf for: Apache, Nginx, Lighttpd, Google App Engine, IIS, NodeJS
* Many small tweaks (read the source comments and full changelog)
* A humans.txt
* All that and we even reduced the overall published size of the boilerplate.
It's not up to the v1.0 release, but it'll get you most of the way there.
What we hope people do is to read through the source to see why we made the choices for defaults and pick and choose what they like and keep using them.
There are lots of defaults that were eye-opening to me that were suggested by the scores of contributors to the project.
The reasons for each of the choices we made is all within the comments of the source file, so it is easier to choose what to keep and what to change.
But browsers are supposed to create HEAD and BODY elements if your markup doesn't include them. However some do not: http://www.stevesouders.com/blog/2010/05/12/autohead-my-firs...
This means everyone's code that does `document.getElementsByTagName('head')[0]` will fail in some cases. Because that is rather risky, we decided to retain these optional elements..
The closing tags for </body> and </html> however...