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.
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 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.
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.
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.
One opt-in exception, scoped tight: turn on auto-approve and Quill will clear the most trivial drift fixes on its own — but only a pure selector swap (a renamed data-testid where the step, its role, and its accessible name are unchanged), and only after a live probe re-verifies it. Anything structural stays in the queue for you. Run it in shadow first to watch what it would approve before it touches anything.
Some features only a human knows about. Click through them once with the Quill Capture extension — it records your actions as a replayable workflow, not a screenshot reel. Quill verifies it can repeat what you did, then generates the same narrated video and article every discovered feature gets. And because it's a workflow, it's enrolled in drift detection forever: record it once, it stays current.
When that feature drifts later, you don't hand-edit anything — you record a correction. Re-capture the feature with the extension and Quill recognizes it already has an approved workflow: instead of publishing over the top, it files a supersede proposal in your review queue. Approve it (or let auto-approve clear it, if it qualifies) and the new version goes live. The fix flows through the same gate as everything else.
Quill remembers which source files cite each stable selector a walkthrough depends on. On every push it re-greps exactly those files — when a function changes signature or a selector disappears, you get a queue entry: "this might be stale." No outdated docs nine months later.
Some features can't be checked against source — third-party surfaces, generated DOM, anything without a stable selector to grep. Those get the other half of the coverage: Quill re-runs the recorded walkthrough on a schedule and files a proposal the moment a step stops reproducing. Code-linked features drift-check on push; un-greppable ones drift-check on a timer. Nothing slips through.
we'll have your first docs site live in under a minute.