open-press

OpenPress · document tree · rendered output · v0.3.0

OpenPress turns a document tree into publishable pages.

Chapters live as MDX, design decisions live as tokens, and the same workspace renders fixed-layout A4 pages, PDF, and a public web reader. 

$ npx skills add quan0715/open-press
View live example
Structured document pages, media assets, and reusable React components combining into one fixed-layout document, then publishing to a web reader and PDF.
Documents, media, and React components compose into one maintainable OpenPress document.

Click to copy · skills install under .agents/skills/, auto-detected by Claude Code, Cursor, Codex, Gemini CLI, Cline, Continue, and 50+ other AI agents.

  • Chapters map to the document table of contents
  • Theme tokens control page rhythm, type, and accent
  • MDX changes re-render into A4 pages and the web reader

Why OpenPress

Your agent edits source; OpenPress renders the document.

Document tree

Chapters are a navigable structure.

The source mirrors the table of contents: cover, chapters, appendix, assets, and config stay in predictable places.

Theme tokens

Design changes are controlled inputs.

Typography, margins, accent color, and page rhythm live in tokens instead of being scattered across one-off CSS edits.

MDX content

Content changes render into pages.

A chapter file can mix prose, figures, callouts, and tables; preview shows exactly what changed before PDF export.

Init -> author -> publish

Talk to the agent. Then inspect the page.

Copy the prompt for the stage you are in. The agent writes into the workspace; OpenPress keeps the result page-safe, reviewable, and ready to deploy.

  1. 1.

    Init the workspace

    Start from title, audience, language, and style pack. The init flow creates a real file structure instead of a blank canvas.

    Using OpenPress, help me initialize a document workspace. Ask for title, audience, language, and style pack, then create the starter project with a first outline.
  2. 2.

    Author with the agent

    Work chapter by chapter. Ask for structure, examples, captions, comparison tables, and tone changes while preview remains the source of truth.

    Use OpenPress writing and hierarchy skills. Turn the current outline into chapter 1, keep confirmed facts unchanged, and mark missing details as [TODO].
  3. 3.

    Export and deploy

    Validate the workspace, render the public reader, export the PDF, and deploy only after confirming the target Pages project.

    Use OpenPress deploy flow. Run validation, render the web reader, export the PDF, and prepare a Cloudflare Pages deploy dry run before publishing.

    openpress:validate openpress:render openpress:pdf openpress:deploy

Agent-readable workflow

Use any agent that can edit files. OpenPress gives it the rules.

The project installs skills that tell your agent where source lives, how chapters should be written, which visual layer owns layout, and what must pass before a document is published.

Source boundary

Edit the real files, not generated output.

The agent sees that chapters, components, media, and theme files are source; PDF, render output, and deploy folders are build artifacts.

Writing rules

Draft as a document, not loose prose.

Audience, chapter hierarchy, table captions, figure placement, and factual TODOs are part of the workflow instead of repeated prompt instructions.

Design rules

Change layout through reusable layers.

Theme tokens, page surfaces, and document components give the agent safe places to adjust typography, rhythm, and PDF-safe visuals.

Release gate

Validate before anything goes public.

OpenPress skills point the agent to validation, render, PDF export, and deploy confirmation steps, so publishing stays a deliberate action.

No project yet?

Author a document in the next minute.

One command creates the workspace; your agent takes it from there. 

$ npx @open-press/cli init my-doc --pack editorial-monograph

Available style packs: editorial-monograph (formal long-form) and claude-document (warm working notes).