documentation build → bound pdf manual
Professional PDFs from your documentation build.
Publication-ready manuals from Docusaurus, Starlight, and MkDocs — rendered locally and checked for missing content.
Self-hosted · Docker / Podman · CI ready
when a website is not the deliverable
Some documentation has to leave the browser.
A manual is a PDF document with a version and a filename. It ships, it is archived, it is handed to someone who will never open your site.
The release ships offline.
An on-premises or air-gapped installation arrives as an artifact, not a link. The manual belongs in it, built from the same tag.
The contract names the manual.
Regulated and tendered deliverables are a numbered document you can archive and point to — not a URL whose content changed last week.
Enterprise customers want the version they bought.
Every version and locale is its own manual, so a customer two releases behind reads the documentation that matches what they run.
The documentation is private.
Rendering happens in your own container, on your own machines. There is no upload and no account: your documentation never leaves your environment.
01 / the workflow
Your site is already built. Ask only for the build directory.
Manuscrio reads a finished Docusaurus, Starlight, or MkDocs build, preserves sidebar order, and produces a numbered, bookmarked manual.
No source plugin. No hosted upload. The command runs Manuscrio's container — the same image on a laptop and inside your release pipeline.
npx manuscrio-pdf export ./build- Docusaurus to PDFevery version, locale and navbar section
- Starlight to PDFthe Astro documentation theme
- MkDocs to PDFthe Material theme
Working examples on GitHub:docusaurus-pdf-exportstarlight-pdf-exportmkdocs-pdf-export
02 / measured on real documentation
Not a toy page. The whole manual.
Every export is audited after pagination. Missing resources and serious clipping stop the release instead of disappearing silently.
03 / inspect the output
A real PDF, inside the page.
Inspect the complete 594-page export of the official Docusaurus Canary documentation: every route in the edition, under its Docs and API navbar sections, numbered, bookmarked, and carrying the site’s own logo. One Site Build, exported at three scopes — the same command, a different --scope.
04 / one annual license
Built for the documentation product, not the seat count.
Every version, locale, manual, developer, machine, and CI runner for one documentation product.
€2,400 / year
- Self-hosted container
- Offline organization license
- No export or page limits
Publishing an open-source product? A project that is public under an OSI-approved license, documentation included, can request an Open Source License at no cost.
the manuscript becomes the volume