Ticket #11300 (closed PLIP: fixed)
Switch to HTML5
|Reported by:||spliter||Owned by:||spliter|
Proposer: Denys Mishunov
Seconder: Alexander Limi
For years Plone has been considered a "cutting egde" in it's support of standards and new technologies. During the last years the new exciting versions of "web cornerstone" technologies like HTML5, CSS3 became more and more popular. Even though these technologies are not complete standards and are still in a review process by W3C it is considered safe to use them in the contemporary projects. Projects like Google, YouTube, TypeKit, Twitter, LinkedIn are already using HTML5 as their main markup language.
The PLIP assumes smooth transition to HTML5 support. Due to excellent backwards compatibility of HTML5 specification pretty much any XHTML can become HTML5 with very few if any fixes. Microformats, ARIA roles, CSS3 and other related technologies are beyond the scope of the PLIP. The PLIP is only about the markup used in Plone.
Proposal & Implementation
As already mentioned almost any XHTML1 document can be considered valid HTML5. Though due to backwards compatibility and current state of HTML5 specification we can not use all new elements introduced in HTML5 we can start by taking a smooth transition path.
First of all we will need to switch the doctype to <!doctype html> - the valid doctype of HTML5. After this the full validation process (for different views) has to be done to spot validation errors and fix those. From my experience of doing HTML5 on Plone it's the matter of a couple of fixes. Might be more in some cases ;)
This will give a very good basis for those who want to use up-to-date technologies. At the same time will let those who want to keep writing XHTML1 keep doing this even though within HTML5 doctype.
The PLIP doesn't need any special deliverables except, updated documentation. Main point - even though HTML5 allows both - HTML (no need to self-close the tags etc) and XHTML styles, templates for Plone should be written in XHTML style to keep them sane and predictable.
Risks are minimal since the HTML5 doctype is very backwards compatible. Though there might be an issue with using DIazo if developers ignore XHTML-style for the markup and write HTML instead. In this case more testing with Diazo should be done.
Denys Mishunov [spliter @ #plone]
comment:81 Changed 5 years ago by esteele
- Status changed from assigned to closed
- Resolution set to fixed
comment:82 Changed 4 years ago by davidjb
- Status changed from closed to confirmed
- Version set to 4.1