Is HTML5 the “Magic Bullet”?

Digital Book World January 14, 2015

Sanders Kleinfeld O’Reilly Media, Inc.

Yes!

Conversion! Conversion!

Conversion!

A Traditional Production Workflow Looks Like This:

Three Standard Production Conversions:

1.  Word -> InDesign to do typesetting = �

2.  InDesign -> EPUB/MOBI for digital = �

3.  InDesign -> Word for next edition = �

How much time/money do these conversions cost your organization?

“…the ultimate goal in creating streamlined publishing workflows

isn’t solely to lower the costs of conversions whenever possible; the aim should also be to eliminate the

need for conversions whenever possible.”

— Sanders Kleinfeld

“The Case for Authoring and Producing Books in XHTML5” Balisage: The Markup Conference 2013 Proceedings

http://bit.ly/1BTGrdH

How we eliminated conversions at

O’Reilly Media, Inc.

We realized HTML + CSS was the common thread for all our outputs

* e.g., AntennaHouse Formatter or Prince!

= HTML + CSS + open source packaging

= HTML + CSS + proprietary packaging

= HTML + CSS + PDF processor*

= HTML + CSS + JS

HTMLBook (github.com/oreillymedia/htmlbook)

We built an open specification for authoring books in HTML5 called:

We built an HTML5 authoring platform:

Atlas (atlas.oreilly.com)

We added CSS template design capabilities to Atlas:

We added one-click publishing to both print and digital outputs:

The Art of Application Performance Testing, Second Edition by Ian Molyneaux (http://shop.oreilly.com/product/0636920033233.do)

Contact Me! Email: sanders@oreilly.com

Twitter: @sandersk