DocumentationDevToolsCLIPublishing

Docs to Book CLI

One CLI that outputs both a docs site and a PDF book

Problem
Technical writers juggle Sphinx, Markdown and PDF toolchains, wanting one CLI to manage both an HTML site and a PDF book while keeping diagrams and reStructuredText extensions. Current setups are complex and error-prone.
Solution
A documentation build CLI: one config outputs both an HTML site and a PDF book, natively supports reStructuredText and CommonMark, and includes diagrams, cross-references and themes. Aimed at technical authors with zero-config start and extensibility.
Users
Technical writers, open-source doc maintainers, and teams that need both web docs and a print book.
MVP
CLI project init; mixed Markdown/rst parsing; HTML site and PDF output; built-in diagrams and cross-references; theme and PDF style templates.
Revenue
Open-source core plus paid themes and hosted build service; or team subscription.
Why now
The Sphinx ecosystem feels dated, AI-assisted writing speeds up content production, yet the publishing toolchain remains fragmented, leaving room for a smoother alternative.

Source discussions · 1

  1. Hacker NewsShow HN: Write once. Explain well. Publish on the web and on paper1↑ 0
← Back to list