Components inside a doc
A doc body can hold the same components your marketing pages use. That means a reference page can carry a live, working example instead of a screenshot of one.
What a directive looks like
Write a single line in your Markdown file:
:::component{slug=features-3col}On import, that line stops being text and becomes a real component node in the doc body — rendered through exactly the same path a page uses.
The result, rendered below
Everything under this heading is a live component embedded in this doc page, not an image:
Built for the way modern teams ship.
Three reasons engineering leads pick us over the alternatives.
Fast by default
Sub-100ms cold starts, edge-deployed everywhere. No tuning required.
Secure end-to-end
SOC 2 Type II, audit logs, granular RBAC. Compliance is the floor, not the ceiling.
Git-native workflow
Every change is a PR. Preview environments per branch. Roll back in one click.
Why this matters
Documentation drifts when the example in the docs and the component on the site are two different things. Embedding the component itself means the doc cannot fall out of date — it is showing the same code your visitors see.