Everything you need to publish, sync and measure your knowledge base.
FOLIO is a knowledge-base platform: publish a typeset, searchable library that syncs with your code and measures what readers actually read. No blank pages, no drifting docs, no wiki graveyards.
Everything runs over https://api.folio.dev. The CLI is the single source of truth: folio init, folio connect, folio publish.
$ npm i -g folio $ folio init ./docs $ folio connect github:acme/api $ folio publish ✓ published · 42 pages · typeset · synced to code
The core commands, in the order you'll use them.
| Command | What it does |
|---|---|
folio init <dir> | Create a knowledge base and its workspace |
folio connect <repo> | Link a repository to sync against |
folio publish | Typeset and deploy your library |
folio draft <endpoint> | AI-draft a page from source code |
folio diff <id> | Review a suggested docs update |
Connect a repo and FOLIO watches every push. When code changes, it flags the pages that reference it and proposes a diff — you review and merge, so docs never drift from the truth they describe.
Give FOLIO a codebase and it drafts the missing pages in your voice, from your existing pages and the source itself. You approve every word before it publishes — the AI is a draft-writer, not an author.
Every paragraph carries a reading metric: completion, scroll depth, search terms, and where readers bail. Write where it matters, and retire the pages nobody gets through.
Docs are encrypted in transit and at rest, and access is scoped with SSO. We are SOC 2 Type II audited and never train on your data.