Every project we undertake will involve doing something we've done before. In fact there are some things we have to do for every project and I'm not talking about our processes or project management milestones. I'm talking code.
“ Think of it as the foundation we lay each time to build the templates on. ”
Now, this sounds a bit tedious, having to write out the same code for each project and that's where boilerplates come in. We have developed two sets of files that we use as the starting point for every project. We have one for XHTML 4.01 and one for HTML 5. Why two? Well HTML 5 is technically still a draft format and some of our clients are focused on older browsers that don't support HTML 5. We appreciate there are workarounds to aid compatibility but if the target browser doesn't support it and we're not using its features then there is no necessity to use it. That said, we are always keen to use HTML 5 where we feel it is appropriate, such as this site and the Badge Collectors Circle website.
Another point worth noting is that the boilerplate should always be reviewed and improved. This is a great advantage to using the HTML5 boilerplate as it is always being updated and they encourage you to tailor it to suit your needs. In fact there are a lot of added extras in the HTML5 boilerplate that you won’t need for every project. Some argue that this makes it less of a boilerplate as you need to remove bits before starting but we think it’s easier to hit delete than go searching for bits of code!