Drupal 8 HTML5 Initiative Roadmap Posted

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
Jacine's picture

Hello All,

The HTML5 Initiative roadmap has been been posted. Please take a few minutes to review it and share your thoughts in the comments (on this page):

http://drupal.org/html5#roadmap

The roadmap includes two phases. The first phase includes some of the easier aspects of the initiative that are significantly important to completing the transition to HTML5. These are sort of like the bare minimum tasks we need to accomplish to effectively switch to HTML5. Currently, help is needed for Phase 1 efforts. Converting our templates and theme functions to use the new HTML5 elements and WAI-ARIA roles, and implementing Form API support for new input types and form elements is where a lot of the work lies. There are summaries & meta issues for both of these linked from the roadmap:

Templates and theme functions

Form API

The second phase includes a combination of some of the harder aspects of switching to HTML5 could mean for Drupal, along with some feature requests that I've heard so far. There are proposals in progress and ongoing work for some of the tasks listed there, but others are missing or just ideas at this point. If there's something in there (or that's not listed) that you want to see happen, please get in touch and start working on a proposal. Also, feel free to post any discussion(s) you'd like to have in this group.

Of course, all of the issues related to the initiative can be found in the issue queue tagged html5. These issues and the posts from this group are also being posted to the @drupal8html5 twitter account. More information about contributing to this initiative can be found here.

Comments

Supported browsers

bstoppel's picture

As HTML5 (especially the more advanced features of CSS3 and Javascript) are out of reach for older browsers, do we need to have a list or a rubric for determining supported browsers? A well-known approach is Yahoo's Graded Browser Support. If something like this is needed, then adding it to Phase 1 seems advisable as it could influence a lot of downstream decisions.

I don't know if a list would helpful or not, or if this is really left to the theme, but I thought I'd ask.

We have a recommended

Jacine's picture

We have a recommended targeted browsers page in the handbook. It needs some updating, as the jQuery list has changed slightly, and we are having discussions to drop IE6 support from Drupal 8 now. Yay! :)

These discussions aren't directly related to the HTML5 initiative though. People have been asking to drop IE6 support for years, and just because HTML5 isn't supported in IE6, IE7 and IE8, doesn't mean we can just drop support for all of them. In order to deal with this problem in core, adding the HTML5 Shiv has been proposed. I posted a summary of the problem and proposed solution and linked to the the issue where it's being discussed in Phase 1 of the roadmap. Feel free to get involved in that discussion if you're interested.

I think you're absolutely right though. It would be helpful to link to browser support page from the initiative page, so I've done that at on this page. Thank you for posting your feedback. :)

My one feedback on the

ericduran's picture

My one feedback on the roadmap is the 3 item (WYSIWYG editor that uses contenteditable)

This is a huge task and something that might be better off in its own initiative.

jQuery.contentEditable looks

seutje's picture

jQuery.contentEditable looks rather promising -> http://freshcode.co/plugins/jquery.contenteditable/demo.html
Aloha as well, but seems a bit heavy...