Disadvantages of the HTML5 boiler

Question

I have been using XHTML for about 3 years, and I really disliked the arrival of HTML5 and CSS3. A few months ago, I came across an HTML5 Boilerplate , and now I'm very interested in this.

The only thing I can not find is the disadvantages of using this set of best practices. I know that the main goal of this is to make the site look the same in a variety of browsers, but is there something I should know about?

Answer 1

Is there anything I should know about?

Yes, definitely. This is not a puzzle game. . Or at least it could be so, but it was not intended for that. And if you use it in this way, you cannot enjoy your best. The boiler is very flexible, and you need to learn how to configure it. Full stop.

My personal suggestion is to start experimenting with him and explore the possibilities that he can offer. Fortunately for us, this is well documented, and you can learn a lot. Not only the template itself, but also the rules and recommendations on HTML5, CSS3, resource loading and related problems / workarounds, browser features and ways to fix them, tricks for developing mobile devices, policies and conditional loading, and much more crazy things. Once you are aware of your capabilities, if you find any flaws, you can customize the basic template.

Start here , read the docs , follow each link and don't be tempted by shortcuts. It takes time, but you will be very grateful. If you have problems, ask.

For something more specific, the drawback that I found very quickly (but someone considers this a plus) is that the template template does not provide a CSS grid. Not a huge problem, I found adapt.js easy to integrate, so I replaced normalize.css with styles.js reset stylesheet and used a grid.

Answer 2

Two things I noticed a couple of months ago are the way to load javascript in the lower body. I am not a big fan of this, if not only does he look dirty. I also tested the download myself and did not notice any better javascript loading. In fact, it ran a couple of ms slower on a huge script.

Also, I tried normalize.css a couple of times, but found that restyling has more paddings and fields than before. This is normal, because the goal is somewhat similar, but different from the other. I changed this to Eric Meyer reset.css just because I got used to it.

I really like modernizr script and the way to implement things for x-browser results. For example, the implementation of Google Analytics.

Another small thing that I remember is the placement of the title tag. I changed it to the top for SEO reasons.