Doc components
Callouts, cards, steps, tabs, accordions, and code blocks you can use when writing docs.
Doc components
These are written in plain markdown with ::: directives — no JSX, no MDX
compilation. Nesting needs more colons on the outer fence (::::tabs
containing :::tab).
Callouts
Use callouts for asides. Types: note, tip, warning, info, check.
Don't run a bare dedupe_df(df) — route through the curated config.
You can give any callout a custom title="…".
Cards
How matching, blocking, and survivorship fit together.
:::
Steps
Connect a CSV or a SaaS source.
Dedupe records into golden records.
Send the golden records to a destination.
:::
Tabs
from app.services import matching
result = matching.dedupe(df)
Accordions
▸Is search a SaaS?
No — it's a static index built at deploy time, searched client-side.
▸Does this use Mintlify?
No. It's hand-rolled in the Next.js docs app.
Code blocks
Fenced code blocks get a copy button, and a filename header from title="…":
export const answer = 42