Anyone using html 5 doctype and its new elements for commercial projects yet?
How about a starting point? Are you using this - http://html5boilerplate.com/ - something else or rolling your own?
What about CSS3 twiddly bits - are we including some, lots or just a few bits?
So much has changed since I last overhauled my project framework and it's looking slightly out of date!
Thought I'd see what you're all doing in case I was missing something.
I'm using the html5 elements that are recognized by lead browsers and degrade gracefully when they are not recognized (ex form elements), as well as the html5 doctype.
Font-face with Google web fonts
CSS3 whenever possible! Graceful degradation for the others!
HTML and CSS
At work, I focus on supporting CSS2 because we have to support all the way back to IE 6. Most of my time is working on getting things working and looking right in all browsers, instead of implementing HTML5 compliant markup or CSS3 styles. Where I can, I do my best to write code that is optimized for new browsers, and do use the
border-radius specification to make things look a little nicer, but this is not a very common thing.
While working on personal projects, however, I do test out the latest technologies like the
<canvas> element and other HTML5 markup. I've yet to play with too much of the CSS3 specification, and browser implementations, but they are next on my list for testing out.
As far as doctype goes, I always use the
<!doctype html>, which defaults to HTML5 support when supported.
Also, I code all of my projects from scratch, or from an existing base that I've programmed. I don't use the boilerplate, though I have looked it over, and seen it in a few places.
I don't do any font replacements or things of this nature as I just use browser defaults. My layouts are dynamic enough to allow for user specified fonts, and I'm not quite a bit enough font-enthusiast to have a desire to use better fonts in my designs. Any time I need custom fonts, I usually have it in an image with graphics, and an
alt attribute fallback, usually with hidden text representing the image as well (not the most accessible at times, but its a bad habit I've developed).
Actually, this is really more suggestions in tools I'd like to see, as I think this is really the base of your question. Personally, as mentioned in the answer by @adelacreative, degradation is an important key at the moment. Too many of the users that visit site I work on are coming from old browsers that don't support these new, fun tools. That said, I would love to be able to capitalize on these technologies, but I don't want to have to program things twice, or even spend a lot of time on features a large portion of my users won't see. Tools that can get me up and running quickly, while still supporting older browsers and out of date users are certainly good. That is why I use tools like jQuery and Prototype, and why I will continue to use them. They allow me to program common code to get the site working across the board. This is, I certainly know, difficult to do very well in non-programming languages, like HTML and CSS, especially with any reasonable sizes (for mobile support especially), but highly desirable.