HTML5 is coming. It is considered fundamentally a part of the strategy for device independence. It is part of the accessibility equation. It is part of the mobility equation, in an increasingly "mobile-first" end user world (e.g. students).
HTML5 - Main topics for 2.x consideration
This is a working page, under construction, for us to gather relevant info about it and its impact on our longer-term strategy. We'll improved the organization and summarize, as we cull through and develop content.
Links to Relevant Resources
- HTML5 & associated CSS3 and ARIA specs:
- W3C working draft (March 15, 2012) of HTML5 spec (this is draft 2 which will be reviewed, updated, edited and recommended to be approved as a standard)
- W3C previous published working draft (May 25, 2011) of HTML5 spec (this is the earlier edited draft)
- http://www.whatwg.org/ - "The WHATWG was founded by individuals of Apple, the Mozilla Foundation, and Opera Software in 2004, after a W3C workshop. Apple, Mozilla and Opera were becoming increasingly concerned about the W3C’s direction with XHTML, lack of interest in HTML and apparent disregard for the needs of real-world authors. So, in response, these organizations set out with a mission to address these concerns and the Web Hypertext Application Technology Working Group was born."
The WHATWG influenced the W3C to restart their HTML effort and remains involved.
- Interactive overviews, demos and code snippets:
- Articles and commentary - HTML5 overviews:
- Tables and tools:
Topics and Questions:
- Should we change default doctype to HTML5 now?
- Can we learn from the server side adaptions mobile providers use to change the doctype from HTML5 to XHTML MP and CSS MP in order to be accessible to new as well as still be accessible to older (phones).
- HTML5 push state - potential positive impact to performance (reduces calls back to the server)
- Native apps vs HTML5 (device independence) - is it an either/or decision, or which will win out in the long run?
- How LinkedIn used Node.js and HTML5 to build a better, faster app
- Responsive web design (1 design supporting all devices):
- Ethan Marcotte quote: "We can design for an optimal viewing experience, but embed standards-based technologies into our designs to make them not only more flexible, but more adaptive to the media that renders them. In short, we need to practice responsive web design. But how?" (CSS3 media queries example)
- Boston Globe website redesign: See article.
- Trans-media design (E.g. CSS3 media-query serving different designs depending on the device characteristics):
- Jakob Nielson quote: "Mobile use will rise, but desktop computers will remain important, forcing companies to design for multiple platforms, requiring continuity in visual design, features, user data, and tone of voice."
- Mobile UI guidelines:
- Windows 7
- Mobile First by Luke Wroblewski: http://www.lukew.com/ff/entry.asp?933
- (Much more to come - work in progress! Stay tuned! Contribute!)
- (Add things here .... )