13 comments

[ 2.2 ms ] story [ 40.0 ms ] thread
I started working on markup for a new site this week and put HTML5 Boilerplate into real use for the first time. It has been a very helpful, time-saving starting point. I'll definitely be incorporating most of it into my "new site" template.
Can someone explain to me why their site - http://html5boilerplate.com/ - uses the <b> and <i> tag?
The <b> tags are used to create the background effects with CSS3 instead of using a background image. <i> is also used as an inline element for semantic and styling purposes.
Whilst I'm pretty sure they're not using those b tags at the top for their semantic purpose (they're forming the cross thing that forms part of the background texture), b and i have both found their way back into HTML5 as fully acceptable and semantic tags for markup: http://www.whatwg.org/specs/web-apps/current-work/#the-i-ele...
I created the design, and it is a deliberate use of those tags to create graphical elements which you can see in the background. It should be diagonal in browsers that support CSS transforms, and vertical in browsers that dont.

http://html5doctor.com/i-b-em-strong-element/

I figured there was a great reason, I just didn't know how to begin finding that answer short of asking the experts.
HTML5 Boilerplate is a really impressive attempt to consolidate all best practices into one template. The comments alone are one of the best sources of documentation for front-end development.

Now the choice is selectively building up your own template for projects, or starting with HTML5 Boilerplate and just keeping parts that are needed. My strategy has been to start with the boilerplate since lots of commonly forgotten "small" details are included by default.

(comment deleted)
We just launched our new website which uses HTML5 Boilerplate (and HAML and SASS, and Rail 3 but that's neither here nor there): http://cubus.ro. Any feedback is welcome and much appreciated, including usage of HTML5 elements.
Wow - the site freezes my Chromium (nightly) tab for it. Never had that happen before for websites - only plugin-related issues. Guess that is what you get for using spankin' new features!
The CSS file is a thing of horrifying beauty. I don't know whether to hail it as my savior or try to drive a stake through it.
What the hell is this?

I think we should seriously think this web thing over.