The last sample – Part IV of the 5DOC series of new offline prototype documents – is the same document as the first sample in native format, but with quasi-offline content supplemented with downloaded data. The content of the other version in Part I was taken from the source of the web page, and this version contains material that is download when the offline page is loaded in a browser.
Don’t take my word for it! Download and load it into a browser tab with a live internet connection and into another tab with the connection off.
OK, so it’s not 100% offline, but it offers an innovative new option. The 5DOC now becomes a living document that is referenced as a file instead of a bookmark or a multistep search and navigate process to find the updated version of a given document.
Open the file in a browser and enjoy an updated version.
Opens the menu modal for both on- and offline samples
Note (11 November 2015): this sample has been unpublished due to a change in approach by 5DOC for producing content with code syntax highlighting. Previously, 5DOC used a WordPress plugin and abstracted the relevant code for the 5DOC downloaded version.
Over time it has become obvious that in fact each sample has a different approach to code syntax highlighting and the goal should be flexibility not consistency. All links below initially to the 5DOC sample, now link to the original content.
Arguments about HTML5 vs XHTML5 are about as clear as a discussion of the difference between General Motors and Opel. Once the “scout” in you indulges in learning, you then discover you have wasted your time. Gut instinct: go with HTML5. Here is one debate.
We have to ask ourselves what is the point? IMHO too much effort is made to make things complicated and less useful–to stay within known parameters. But why do we need e-readers when we have browsers and why do we need XHTML5 when we have JSON?
WordPress.org is busy developing the capability to represent WordPress content with JSON Rest API. And there is already interest in extracting JSON from EPUB. So it is very realistic to project the capability to go from WordPress ⇔ HTML5 and from other forms of data structure ⇒ (WordPress || HTML5).