Convert core templates and theme functions to HTML5 - Meta Issue

A huge part of this work has been done in HTML5 Base. Also, see http://groups.drupal.org/html5

Most of the work done on html5_base wasn't done as just a base theme, but as an HTML5-ified version of the core templates. You are duplicating work, but more importantly duplicating the effort. Perhaps join us in #drupal-html5 sometime to discuss it?

You've just edited all your comments, and I'm not sure what they said the first time, so whatever. They all seem more positive now, so I'll respond in kind:

Your insight and effort on HTML5 is awesome, and I'm glad we have the same goals for core.

At DrupalCon Chicago, we had a redirect made for http://drupal.org/html5, and we'll be focusing our discussion around that and the pending HTML5 forum, so as to not go "off-topic" on these threads.

I love actionable issues rather than 200 comment long discussions! Thanks for splitting this up, Jeff.

sorry, but subscribing

Thanks for creating all these issues Jeff! :D

Subscribing, can't wait to help out on this

Subscribing!

Subscrizzle

subscribing

At this point this issue is just noise in the issue queue. The official page is here, so closing this.

There's no decent/easy way to keep up with changes there like there is with the "follow" feature on issues. One has to bookmark the page, then visit from time to time then check the revision diff. I personally really prefer to keep this issue here updated. So, can we please keep it open until we address #1304216: A user should be able to "follow" individual pages of content and receive email notifications for new comments.

...I meant that I need to use the diff on docs (like the one Jacine links to in #16) - not on issues. I do this with issue summaries too, but usually when one updates an issue summary they also post a comment. Even if they choose to update the issue summary without leaving a comment, still the issue dashboard shows a "new" link to denote the issue as updated. We currently don't have this feature with documentation nodes AFAIK. One has to "manually" visit them and remember their last update date and compare it to what they see when they revisit. If the date is different, they see the revision diff in order to know what's changed. That's way too much "manual" work and seems tedious to me.

But then we have two resources to update...

Yes, so let's update this one and ditch the other then. It is a list of issues after all. That translates as a meta-issue to me - not a documentation page. I'm ok with keeping the first section (the "New HTML5 Elements" part) in docs since it fits there, but the list of issues belongs in a meta-issue (with status, priority, tags, update notification in the "my issues" dashboard and all).

The official page is here...

I honestly don't get what makes that page "official" and this issue here not. I see some discussion here and at the same time no comments to that documentation node whatsoever. I think that issues should remain open in the issue queue where they belong and once/if they are resolved, their outcome should be posted in the appropriate section of the documentation. The only issue link that should be in that doc node should be one linking to this issue here.

PS: in an ideal world, we'd have: #44162: Relationships between issues: support for parent issue and related issues and #1300972: Implement initiative content type that would make all this less painful.

added new template issues