Repository navigation
HTML book output: several outputs per project, installable offline ebook #13
Description
Problem
A scriptorium project renders to one PDF. A book that should also be read on screens needs a separate toolchain, and there is no way to get the same book as PDFs of different page sizes.
Proposal
Spec: docs/superpowers/specs/2026-10-20-html-book-design.html. Plan: docs/superpowers/plans/2026-10-20-html-book.html.
outputs:inscriptorium.yaml: several PDFs (each may override the page size) and anhtmloutput.- The
htmloutput is a static directory: an ebook reader paginated by CSS multi-column layout (swipe on phones, two facing pages on wide screens), installable as a web app, readable offline, and updated automatically when the book changes.
Delivered in three stacked PRs: outputs; the HTML book; installable and offline.
Supersedes the 2026-08-14 HTML ebook spec, which left offline reading out.
Activity
feat: several outputs per project (#14)
feat(reader): one chapter at a time
feat: the HTML book output (#15)
fix(reader): page counts do not depend on fonts or images having loaded
test(reader): update tests ask for the new edition until it lands
feat: the HTML book installs and reads offline (#16)
apiad commentedon Oct 20, 2026
Done in #14 (outputs), #15 (the HTML book, one chapter per file) and #16 (install, offline, updates).