I Bypassed Adobe and Microsoft to Build a Git-Tracked Book Production Pipeline

I Bypassed Adobe and Microsoft to Build a Git-Tracked Book Production Pipeline

Hacker News
Hacker NewsMay 22, 2026

Why It Matters

The workflow demonstrates how independent authors can cut costs, improve quality control, and gain full ownership of their publishing assets, challenging the reliance on expensive proprietary software. It signals a shift toward open‑source, automated publishing pipelines in the indie‑author market.

Key Takeaways

  • Author built Git‑tracked pipeline replacing Word, InDesign, Kindle Create
  • Used ODT as source, converted to XHTML and TeX via custom script
  • Standard Ebooks linter ensures EPUB quality and accessibility
  • LibreOffice, Calibre, Pandoc, and LaTeX form open‑source workflow
  • Reproducible PDFs and EPUBs generated without proprietary software

Pulse Analysis

Independent authors are increasingly treating book production like software development, applying version control and automation to achieve professional results. By adopting LibreOffice Writer for semantic ODT files and scripting conversions to XHTML and LaTeX, the author sidesteps costly tools such as Adobe InDesign and Kindle Create. This approach not only reduces licensing expenses but also creates a transparent, auditable history of every change, allowing editors and proofreaders to collaborate via Git diffs—a practice familiar to developers but novel in publishing.

The integration of the Standard Ebooks style guide and its automated linter adds a layer of quality assurance previously reserved for large houses. The linter checks typography, metadata consistency, and semantic markup, ensuring EPUBs meet strict accessibility standards and render uniformly across devices. Coupled with Calibre’s robust conversion engine, the pipeline produces clean, device‑agnostic files that upload seamlessly to platforms like KDP, eliminating the need for multiple proprietary conversion steps.

Looking ahead, the open‑source stack—LibreOffice, Pandoc, LaTeX, and custom Python scripts—offers scalability for larger projects and potential community contributions. As more indie writers adopt similar pipelines, the publishing ecosystem could see a democratization of high‑quality typesetting, reducing the barrier between creative writing and professional production. This shift not only empowers authors financially but also encourages innovation in tooling, fostering a more resilient and flexible self‑publishing landscape.

I Bypassed Adobe and Microsoft to Build a Git-Tracked Book Production Pipeline

Comments

Want to join the conversation?

Loading comments...