HTML5 Boilerplate is the professional badass’s base HTML/CSS/JS template for a fast, robust and future-proof site.

After more than two years in iterative development, you get the best of the best practices baked in: cross-browser normalization, performance optimizations, even optional features like cross-domain ajax and flash. A starter apache .htaccess config file hooks you the eff up with caching rules and preps your site to serve HTML5 video, use @font-face, and get your gzip zipple on.

Boilerplate is not a framework, nor does it prescribe any philosophy of development, it’s just got some tricks to get your project off the ground quickly and right-footed.

http://html5boilerplate.com/

Via Benjamin De Cock (@deaxon)

There’s also an HTML5 reset:

Like a lot of developers, we start every HTML project with the same set of HTML and CSS templates. We’ve been using these files for a long time and we’ve progressively added bits and pieces to them as our own personal best practices have evolved.

Now that modern browsers are starting to support some of the really useful parts of HTML5 and CSS3, it’s time for an update, and we thought we’d put it out there for everyone to use. By no means do we see this as the end-all and beat-all, but we think it’s a fairly good starting place that anyone can take and make their own.

http://html5reset.org/

And even am HTML5 site template to get started:

The whole point of this is to abstract things I do over and over again when starting a new web design/development project. This reflects my workflow and may change over time because of that.

http://github.com/dcneiner/html5-site-template

so instead of listening to the window for keypress events:

$(window).keypress(function(){...});

I had to do this:

$(document).keypress(function(){...});

I prefer working with the nightly build webkit, mostly because the web inspector had a full redesign. Before I used firefox with a gazillion addons ending up using only firebug… And speaking of firebug, check out the firebug lite bookmarklet, ideal for Internet Explorer issues. And not to forget dragonfly for those who use opera.

But maybe, you’re like a taxi driver, you give them an estimate and if the client agrees you start working. If you deliver on time the pay less, if the job takes a little longer, the customer pays more. I believe this is the most fair way to work, unfortunately web development seems to be in the dark zone for most people, as if we just click buttons on some kind of magic box that does all our work.

So how do you bill your clients?

More videos and info about this concept can be found on: thefuntheory.com