Probably way too harsh - BP gives the minimum that you can try and plug your own code into.
html5bones is clearly taking a different route, by making everything and every tag as clear as possible. Everything is commented to give someone starting out a good explanation of why all this stuff is there.
Newbies are now completely lost. What's going on here?
html5bones:
<!-- An <aside> is used to enclose content that is additional to the
main content but not essential. If it were removed, the meaning of
the main content should not be lost, but the content of the <aside>
also retains its meaning. -->
<!-- ARIA: the landmark role "complementary" is added here as it
contains supprting information for the main content that remains
meaningful even when separated from it -->
<aside role="complementary">
I heavily applaud this idea - too much of HTML best practices is completely arcane to most of the people using it. The more people understanding what this stuff actually does the better for everyone.
Hi, I wrote HTML5 Bones and to be fair Simon has a good idea (detailed in the GitHub pull request) in that there should be two versions, a file with all the comments and one without - and so catering for both types of users.
I definitely don't want to remove the comments as they are integral to what I want the "template" to help people do.
html5bones is clearly taking a different route, by making everything and every tag as clear as possible. Everything is commented to give someone starting out a good explanation of why all this stuff is there.
eg. in HTML5 BP:
Newbies are now completely lost. What's going on here?html5bones:
I heavily applaud this idea - too much of HTML best practices is completely arcane to most of the people using it. The more people understanding what this stuff actually does the better for everyone.