Oreilly
0 likes357 views
HTML5 is proposed as the future of book authoring. Traditional publishing involved writing, conversion to different formats, and printing. Digital publishing added ebooks. The document advocates writing directly in HTML5 rather than converting between formats like DocBook XML or Markdown. This reduces complexity and troubleshooting headaches. Authors also generally prefer visual editors over markup languages. The future of authoring involves visual, web-based editing with version control and seamless production of HTML5, ebooks, and print.
Oreilly
- 1. HTML5 Is the Future of Book Authorship Digital Book World January 14, 2014 Sanders Kleinfeld OReilly Media, Inc.
- 2. The Goal of Publishing: Packaging and Distribution of Ideas
- 3. Publishing!
- 5. Traditional Publishing Process! (Writing!) (Conversion!) (Printing!)
- 7. (Post)Modern Publishing Process! (Both Print and Digital) (Writing!) (Conversion!) (Conversion!) (Printing!)
- 8. Welcome to Conversion City Enjoy Your Stay Conversion! Conversion! Conversion!
- 9. The Single-Source Solution: Replace conversions with semantic markup and automated transforms <!/>!
- 10. How We Did It: 1. Encourage authors to write in DocBook (heavyweight, semantic XML markup) or AsciiDoc (lightweight, semantic wiki-like markdown) 2. If authors prefer to write in Microsoft Word ("), let them ("""), but convert to DocBook when book goes into Production 3. Maintain a customized version of the DocBook project stylesheets for automatically generating print/ebook outputs
- 11. OReillys Single-Source Workflow (2006-2013): AsciiDoc DocBook XML asciidoc.py DocBook XSL EPUB Stylesheets + Custom CSS EPUB DocBook XSL HTML5 Stylesheets HTML5 Print PDF Web PDF AntennaHouse + Print CSS3 AntennaHouse + Web CSS3 EPUB DocBook XSL EPUB Stylesheets Custom XSL for EPUB postprocessing + KF8/Mobi7 CSS Mobi-ready EPUB Kindlegen Mobi (KF8)Source Content Intermediate Output Final Output For Sale (optional; can start with DocBook)
- 12. Three Slowly Dawning Realizations About Our Workflow
- 13. Realization #1: Our toolchain is rather heavyweight, complex
- 14. PDF* Toolchain Stats The DocBook project XHTML5 stylesheets** contain: ≒ 33,707 lines of HTML-generation code ≒ which rely on 8,346 lines of common dependencies Or, in terms of functions, they contain: ≒ 1,857 <xsl:template>s ≒ which rely on 272 common dependency <xsl:template>s * Separate code base for EPUB/Mobi! ** docbook-epub3-addon-b3!
- 15. When doing transforms, this complexity is a necessary evil, emphasis on evil
- 16. Peril of a Transform- Heavy Workflow:
- 17. Troubleshooting is a real $!%#@&*
- 18. An example! Lets say your DocBook source is: <div class="chapter">! <h1>Poodles and Cookies</h1>! ...! </div>! And your desired/expected HTML output is: <chapter>! <title>Poodles and Cookies</title>! ...! </chapter>!
- 19. But then you run your transform <p class="sect1">! <h2>Poodles and Cookies</h2>! ...! </p>! <chapter>! <title>Poodles and Cookies</title>! ...! </chapter>! And you say, What the $!%#@&*? 33,707 lines of code
- 20. What about implementing validation to preemptively catch errors before running the transforms?
- 21. book.xml:2192: element chapter: validity error : Element chapter content does not follow the DTD, expecting (beginpage? , chapterinfo? , (title , subtitle? , titleabbrev?) , (toc | lot | index | glossary | bibliography)* , tocchap? , (((calloutlist | glosslist | bibliolist | itemizedlist | orderedlist | segmentedlist | simplelist | variablelist | caution | important | note | tip | warning | literallayout | programlisting | programlistingco | screen | screenco | screenshot | synopsis | cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | para | simpara | address | blockquote | graphic | graphicco | mediaobject | mediaobjectco | informalequation | informalexample | informalfigure | informaltable | equation | example | figure | table | msgset | procedure | sidebar | qandaset | task | anchor | bridgehead | remark | highlights | abstract | authorblurb | epigraph | indexterm | beginpage)+ , (sect1* | refentry* | simplesect* | section*)) | sect1+ | refentry+ | simplesect+ | section+) , (toc | lot | index | glossary | bibliography)*), got (para title para para para sect1 sect1 sect1 sect1 sect1 sect1 sect1 sect1 sect1 sect1 sect1 sect1 )! </chapter>! Validation is still troubleshooting: Again you say, What the $!%#@&*?
- 22. Streamlining Production Workflows isnt just about automating conversions whenever possible Its about eliminating conversions whenever possible!
- 23. DocBook Why not seriously consider: HTML Rather than build a toolchain around: InDesign HTML Or: MS Word HTML Or: HTML HTML
- 24. Realization #2: HTML5 Is Ideal for Digital-First Content
- 25. Digital-First Content Development When doing digital-first (ebook/web) content development, these are the key output formats: ≒ EPUB (2.0 and 3.0) ≒ Amazon Kindle Mobi (Mobi7/KF8) ≒ PDF ≒ HTML * docbook-epub3-addon-b3!
- 26. The Common Thread: HTML + CSS * e.g., AntennaHouse Formatter or Prince! = HTML + CSS + open source packaging = HTML + CSS + proprietary packaging = HTML + CSS + PDF processor* = HTML + CSS (duh!)
- 27. Interactivity/Multimedia Is Ultimately All About HTML5 <canvas> or <svg>! ! <audio>! ! <video>! ! <math>! ! ! Animation/Games Music/Narration Video Clips Math Equations
- 28. Its way easier to do stuff like this: If you start with HTML5
- 29. Its way easier to do stuff like this: If you start with HTML5
- 30. Realization #3: Authors Generally Dont Want to Deal with Markup
- 31. Authors prefer visual authoring platforms because
- 32. Nobodys going to learn your markup language Books in Browsers 2012: Liza Daly & Keith Fahlgren, The self-publishing book http://www.youtube.com/watch?v=UWftLHopWQ0#t=5m25s
- 33. Non-Technical Authors Dont Like This <?xml version="1.0" encoding="utf-8"?>! <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" ! "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">! <chapter>! <title>Autobiography of Me</title>! <para>I was born in 1980, I love chocolate ice cream, and I am a <emphasis>wicked awesome</emphasis> writer, yo!</para>! </chapter>! DocBook
- 34. Non-Technical Authors Will Sometimes Tolerate This == Autobiography of Me! ! I was born in 1980, I love chocolate ice cream, and I am a _wicked awesome_ writer, yo!! AsciiDoc
- 35. Non-Technical Authors Really Want This Microsoft Word
- 36. But This is the Future of Digital Content Creation:
- 38. OReilly Atlas (Short and Long-Form Print, Digital, and Web Publishing)
- 39. Next-Generation Content Authoring = ≒ Visual Editing ≒ Web-Based (Responsive Design) ≒ Version-Controlled ≒ Seamless
- 40. Visual Editing
- 43. Two Questions About Your (e)Books Editorial Lifecycle 1. Will more than one person be working on the manuscript files? 2. Will there be more than one draft of the manuscript?
- 44. If you answered yes to either question, you need a version- control system.
- 45. Key Feature #1 of Version Control: Revision Snapshots
- 46. Key Feature #2 of Version Control: Diffing
- 47. What if we versioned manuscripts like software developers version code?
- 48. Revision snapshots tudes for Elixir: https://github.com/oreillymedia/etudes-for-elixir
- 49. Diffing tudes for Elixir: https://github.com/oreillymedia/etudes-for-elixir
- 51. Step #1: Author!
- 52. Step #2: Build!
- 53. Step #3: Review Results!
- 54. All Roads Lead to HTML5
- 55. But Is It Semantic Enough for Book Publishing?
- 57. HTMLBook = ≒ Open Spec for Book Authoring ≒ Subsets XHTML5 Vocabulary and Content Model ≒ Adds Book-Specific Semantics (e.g., <section data-type="chapter>)! ≒ Open Source Tooling for Producing Ebook Outputs
- 58. HTMLBook Sample (github.com/oreillymedia/HTMLBook/blob/master/samples/ htmlbook.html <html xmlns="http://www.w3.org/1999/xhtml">! 油油<head>! 油油油油<title>HTMLBook Sample</title>! 油油</head>! 油油<body data-type="book" id="htmlbook">! <section data-type="chapter" id="chapter01">! 油油油油油油 <h1>Chapter 1. HTMLBook Markup</h1>! 油油油油油油油油 <p>This chapter describes and demonstrates the types of markup<a data-type="indexterm"油油data- primary="markup" data-secondary="types of"></a> that might appear in a chapter. See <em>mappings.asciidoc</em> for more information. HTMLBook borrows much of its semantics油from the EPUB 3 specification, as applied via the <a href="http://idpf.org/accessibility/guidelines/content/ semantics/epub-type.php"><code>epub:type</code></a> attribute.</p>! </section>! </body>! </html>!
- 59. OReillys Single-Source Workflow (2006-2013): AsciiDoc DocBook XML asciidoc.py DocBook XSL EPUB Stylesheets + Custom CSS EPUB DocBook XSL HTML5 Stylesheets HTML5 Print PDF Web PDF AntennaHouse + Print CSS3 AntennaHouse + Web CSS3 EPUB DocBook XSL EPUB Stylesheets Custom XSL for EPUB postprocessing + KF8/Mobi7 CSS Mobi-ready EPUB Kindlegen Mobi (KF8)Source Content Intermediate Output Final Output For Sale (optional; can start with DocBook)
- 60. OReillys Single-Source Workflow (2014!): XHTML5 EPUB Print PDF Web PDF AntennaHouse + Print CSS3 AntennaHouse + Web CSS3 EPUB Custom XSL for EPUB postprocessing + KF8/Mobi7 CSS Mobi-ready EPUB Kindlegen Mobi (KF8) Source Content Intermediate Output Final Output For Sale Packaging XSL + CSS Packaging XSL + CSS
- 61. Contact Me! Email: sanders@oreilly.com Twitter: @sandersk