Maybe you're trying to fix something that ain't broken, Michelle? What exactly is your goal here? This is where you have to start, not with the technical choices part. Or rants about this 2 and that 5.
'Cos I can tell you straight I can give a crap about 2.1 or 3 or 4 or 5 or DOCTYPE values.
It's all about how you want it to be, it's not about the personal choices of the developers you're hiring, or about the personal choices of people in forums. They have to be able to deliver all, you just have to tell them
what!. Because a free advice is always unaccountable.
Some tell you 3 is not yet ready. Others will praise 3. Guess what, 2.1 is actually still not yet ready. It's just that *NOW* it has a better "coverage" than 3. While 3 may solve some problems more easy *BUT* with a performance penalty.
And HTML5 is pretty much HTML4+new concepts. So you can actually be safe using HTML5, it allows for full backward compatibility,
if that's what you want.
<hr>
To summarize.
It's not about HTML4, HTML5, CSS 2.1, CSS3. It's not about a DOCTYPE. It all depends on what you're looking for, your "parameters". And this here is a long long talk.
But, in the end, a good developer is able to
accommodate you and your goals and put all this futile talk about numbers and versions aside. And, in my opinion, a good developer will *HAVE* to know how to code using HTML5 and CSS3 *ALSO*, even if you, personally, are not asking for that, on a particular project. It shows that it has a healthy dose of interest in new stuff and it's still in the game, not on way to retire.
<hr>
So, what do you want,
exactly, in your site to change, not in developer's choices?

Bookmarks