With old style theming in a package you could base your themes on Sunburst or classic. Creating themes based on frameworks got me to do the theming on the content side and then move the complete body over to the theme side. After several variations of one type of framework the constant duplication of resources, made me realize I needed some form of inheritance for this type of diazo theme.
So everything you needed to do for xdv to get it to go HTML5 is now no longer necessary. I thought I'd have to use a registry.xml to be able to have a HTML5 doctype, which wouldn't help much with the zip deployment of themes. But yesterday I saw it set in a manifest.cfg on the ploneconf (2011).
The greatest thing to me about XDV is that you can leave Plone as it is and alter nearly everything about it. Mostly xdv will suffice, but when necessary you can even grab for xsl. You're not even doctype bound. I've been working on an XDV theme based on HTML5 boilerplate.
With Plone's new theming mechanism it is a breeze to conform to a strict doctype necessary for the Dutch Web-guidelines (Webrichtlijnen Overheid). This post is actually long overdue since I've done this at least half a year ago, but still, better late then never.
The installation of python2.4 on Ubuntu 10.04 had me pulling the hair from my head. I needed to deploy a Plone project using Fabric and buildout-source-release and python2.4, but the latter has been dropped for Ubuntu 10.04. Through dirty hacks it was possible to release, but now I've got the propper solution.