A single doc — no site needed
superlore isn't only for full docs sites. Author one superlore-compatible .mdx and open it instantly in the editor preview or the online Viewer — no deploy, no KB.
A superlore KB is the full experience — a deployed site + an MCP. But the atom is a single
.mdx. Any one superlore doc — a spec, a brief, an architecture write-up, a runbook — opens and
renders on its own, no project and no deploy required.
Two ways to open one doc
Why this matters
- Lowest friction
- One file is the on-ramp — try superlore without scaffolding a project.
- Hand it over
- Send a teammate the .mdx (or a bundle with your comments); they open it in the Viewer and see exactly what you see.
- Agent-ready already
- Even a single doc is dual-representation — the rendered page and the typed knowledge are the same source.
- Grows up cleanly
- When one doc becomes many, scaffold a KB and drop the files into content/docs.
It just has to be superlore-compatible MDX
Any .mdx using superlore components (or plain Markdown) works — there's no project boilerplate
to satisfy. The Viewer and the editor extension both render the same component set this
site uses.
When you outgrow one file
Start with one doc
Author a .mdx, preview it in the editor or the Viewer, iterate.
Scaffold a KB when you have a few
Run the superlore scaffold (or ask your agent), then move your .mdx files into content/docs/.
Deploy + connect the MCP
Ship it anywhere; your agents read the whole corpus over /api/mcp.