The best in migrating to HTML5 is that (x)htlm4 doesnt care about new semantics and HTML5 does not care rendering old styled html, as far as I know. So there is nothing to worry about. Plugins will drop in by time. If'd be nice to have core plugins like staticpages to be in HTML5 semantic, no question. But there is not need to bundle the release dates, if the template is well done earlier.yellowled wrote:So what do we do about plugins then? At least some plugin would have to emit HTML5 code as well, otherwise the whole thing would be pointless. Do we maintain seperate legacy versions? Or do plugins have the ability to emit HTML4, XHTML and HTML5 code? Wouldn't that be bloat?
Btw, do all other old templates now fall back to 2k11 and bulletproof, or just one of them, or none?