[ how it works ]

your code in,
three docs out.

Quill plugs into your repo, reads what you've built, and generates the help center, dev reference, and blog your users actually need. Here's the loop in detail.

/01

point quill at your repo.

One command. Give Quill read access to your GitHub repo and the dev URL of your running app. No SDK to install, no annotations to litter your code, no schema to define.

quill · your-project
$ npx quill init
→ paste your repo URL: github.com/you/your-app
→ paste your dev URL: http://localhost:3000
✓ connected.
$
/02

it discovers what your app does.

Quill walks your codebase — routes, components, types, data-testids, comments, tests. It builds a feature catalog: every "thing a user can do" in your app, indexed and ready to document.

📁 apps/web/src/app
📁 flows
📄 page.tsx flows_list
📁 [id]
📄 page.tsx flows_detail
📁 new
📄 page.tsx flows_create
7 features discovered
/03

three docs from one source.

For each feature, Quill plans a workflow, runs it in a real browser, records the screen, narrates over the recording, and drafts the matching MDX. Help center walkthroughs, dev-doc references, blog posts — all from the same source, all cross-linked.

feature
help center
walkthrough · video · steps
dev docs
reference · params · examples
blog
launch post · changelog entry
/04

you review before anything ships.

Every artifact lands in your review queue. Approve, edit inline, or re-record a step with the browser extension. Edits survive re-runs. Nothing publishes without you.

new
how to create a flow
help-center · 2:14 video · 4 steps
drift
POST /api/flows reference
dev-docs · params changed in #1284
live
bulk-edit support — launch post
blog · published 2 hours ago
/05

drift detection keeps it honest.

On every push, Quill diffs your code against the docs it generated. When a function changes signature or a walkthrough's selectors disappear, you get a queue entry — "this might be stale." No outdated docs nine months later.

quill · drift detected
$ git push origin main
→ quill detected 1 commit, 4 files
⚠ 3 dev-doc pages affected by apps/api/routes/charges.ts
⚠ 1 walkthrough may need re-recording
✓ 4 changes queued for review
$

see it on your repo.

connect a repo →

we'll have your first docs site live in under a minute.