How I Built an Automated Ebook Production Platform—And You Can, Too! - Nellie McKesson - ebookcraft 2017
•
2 likes•1,902 views
HOW I BUILT AN AUTOMATED EBOOK PRODUCTION PLATFORM—AND YOU CAN, TOO! AUDITORIUM MARCH 23, 2017, 2:40 PM-3:25 PM NELLIE MCKESSON Senior Manager, Content Workflows, Macmillan Automating ebook production can seem daunting, but there are a lot of tools already out there that can help you along. If you don’t try to build a rigid, everlasting, and unbreakable automated toolchain, but instead think about the points of change and build around them, then the task of automating becomes much less scary. Get a first-hand look at a successful case study and get some practical guidance for building functions that work smoothly and meet user needs. March 23, 2017
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (16)
More from BookNet Canada
More from BookNet Canada (20)
Recently uploaded
Recently uploaded (20)
How I Built an Automated Ebook Production Platform—And You Can, Too! - Nellie McKesson - ebookcraft 2017
- 1. How I Built an Automated Ebook Production Toolchain (and You Can Too!) Nellie McKesson, Macmillan Publishers
- 4. Output fileInput file Some scripts What is Automation?
- 6. EPUB Microsoft Word InDesign In-House External Vendor The Existing Process:
- 7. Make ebooks in house, minimize overhead 💰🕖👥
- 8. What's the larger goal? What are the initial requirements? What things might change? What things will always be the same? Is there anything already built that I can use? Who is going to be running the tool?
- 9. What’s the larger goal?
- 10. Build an automated ebook production tool that can scale
- 11. The Requirements
- 24. 🙇
- 26. <title>ALICE’S ADVENTURES IN WONDERLAND <author>Lewis Carroll <chapter-title>CHAPTER 1. Down the Rabbit-Hole <text-standard>Alice was beginning to get very tired of sitting by her sister on the bank, and of having nothing to do: once or twice she had peeped into the book her sister was reading, but it had no pictures or conversations in it, ‘and what is the use of a book,’ thought Alice ‘without pictures or conversations?’ Tagging, the Old Way
- 27. .docx = XML
- 28. Styles in Word
- 32. EPUBWord These transformations always stay the same Trans- formations
- 33. Is there anything already built that I can use?
- 34. ?
- 35. Markup
- 36. HTML
- 37. HTML = XML HTML = EPUB HTML = Web HTML + CSS = Print
- 38. HTML = XML HTML = EPUB HTML = Web HTML + CSS = Print
- 39. HTML = XML HTML = EPUB HTML = Web HTML + CSS = Print
- 40. HTML = XML HTML = EPUB HTML = Web HTML + CSS = Print
- 41. HTML = XML HTML = EPUB HTML = Web HTML + CSS = Print
- 42. We need to standardize
- 43. A standard is a set of rules
- 44. “HTMLBook is an open, XHTML5-based standard for the authoring and production of both print and digital books.” http://oreillymedia.github.io/HTMLBook/
- 45. Why HTMLBook: • Familiarity • Well-tested and actively updated • Open-source
- 51. Word EPUB
- 55. mammoth.js
- 57. EPUB HTML Book HTMLWord Consistently styled paragraphs Word styles preserved as HTML class names
- 58. Rules: IF class = “ChapterTitle” THEN convert to <h1> Class name What to do with it
- 59. File 1: Transformations: IF class = [Read class names from other file] THEN convert to <h1> File 2: List of Class Names: Heading styles: ChapterTitle PrefaceTitle AppendixTitle …
- 65. Use your best judgment
- 71. HTMLBook Scripts.xsl HTML Book Word mammoth.js EPUBHTML HTML Book Transform.js JavaScript + node.js XSLRuby List of class names .json trans- forms .js
- 72. 📁 📁 Word file IN EPUB OUT
- 73. Design
- 74. Corrections
- 76. Initial Scope Limitations ✅ New imprint ✅ E-only books ✅ Egalleys ⛔ Traditional print books
- 77. Some lessons: You don’t always need to automate everything: sometimes workflow is the solution You don't need to build everything from scratch Build a system of interconnecting tools Solve small problems, one at a time Design for change