HTML5 Sub-theme

My "current" plan was to convert the full Omega package to HTML5+RDFa compatible, but have yet to have the time to do so...

I don't think it'd really be too hard to do...

My main question I guess would be....

A.) Should Omega itself (as the base theme & starterkit) be fully HTML5

or

B.) Should there be a subtheme of Omega that just overwrites all the templates (Omega & Drupal core) to be HTML 5? (which would likely provide it's own starterkit) So in this instance the subtheme of omega would be it's own base theme so the structure below it would be

Omega -> HTML5 Omega Base -> HTML5 Omega subtheme

What are your thoughts there?

@jackinloadup

I'd love your feedback on my previous response... Trying to figure out the best plan of attack for this.

I suppose it depends if you want really light base and heavy subtheme, or heavy base and light subtheme, I choose the latter. Since you basically have to run some alters etc its gonna make sense to do that in base, unless you really really do want to support XHMTL.

You're right that its "not that hard", just different and needs some lateral thinking to workaround some hairy issues such as outlines/sectioning issues such as when to use the various elements, I think between Sky, Adaptivetheme and Boron there are good examples - you might be shocked by how many tpls there are to mess around with:)

HTML5 is totally usable right now, so why not, I got over 1200 users running AT7 and no complaints, not one actually directly associated with HTML5 usage.

I personally don't use your theme, but would love to see more HTML5 starter themes, I think we can really push HTML5 in Drupal - you have a very good starter theme and it could be even better!

HTML5 all the way. Sneaking up on it will eventually lead to fixes that need to be made in 2 places (or more) and a very difficult time for those not so well versed in tpl writing. HTML5 is as much a headspace as anything else.

Keep up the great work.

@Jeff Burnz, @Steven_NC

Thanks for the responses. I've been toying with this in my head for a bit, trying to follow the work you are doing with AT on HTML5, Jeff...

My main "issue" here (and I've had a lot of in person discussions about it with people) was if I should completely redo the templates in the Omega base, or just do it as it's own starterkit.

Hopefully I can get this implemented quickly with the examples provided in current D7 themes.

Marking as fixed.

Beta1 release (now live) offers HTML5 support in the base theme and starterkit.
Please create new issue(s) for any HTML5 related bugs.

@Jeff
Thanks for the bit of advice there, I used your examples in AT and a couple ideas from Boron to go with the first implementation here.