Meridian — Docs & API Reference
A documentation theme built as a reading surface, with the four interactions a docs product is expected to have.
- 54 / 54
- light / dark tokens
- 2
- modes, both designed
- 1
- DOM, rendered twice
- unlimited projects, client work included
- 12 months of updates
- 14 days, no questions
AGENTS.md and 4 skills ship in the zip, so your own agent keeps changing it after you buy.
docs — install, use, customizepages, composed from 11 sections
Every page is a real render from the publish gate, in the mode on show. Open any of them in the live preview.
- Halyard docs — queues over HTTP/
- site-header
- docs-hero
- quickstart-panel
- support-strip
- site-footer
Guides — deliver your first message/guides- site-header
- guides-shell
- site-footer
API reference — endpoints and parameters/api- site-header
- api-reference
- site-footer
SDKs — TypeScript, Python and Go clients/sdks- site-header
- sdk-shell
- site-footer
Changelog — every API release, newest first/changelog- site-header
- changelog-log
- site-footer
Support — how to get help with the API/support- site-header
- support-desk
- site-footer
Terms and policies — agreement, retention and availability/legal- site-header
- legal-desk
- site-footer
Design system — every part, labelled/components- site-header
- docs-hero
- quickstart-panel
- guides-shell
- api-reference
- +6
Prose stops at a ruled line and only machine content crosses it: the reading edge runs down every article column, and code blocks, parameter tables and the architecture figure are the things allowed past. Eight routes ship and every link on them resolves. The SDK page is one tabbed comparison of the same consumer in TypeScript, Python and Go, and a hash selects the language. The release log filters by tag. The reference carries a request builder that assembles a real curl command from the publish parameters and never pretends to send it. The header carries a light/dark switch, because dark here is a designed second table, not an inversion. Search is keyboard-first and opens on the platform's own modifier, every code block copies, and the delivery diagram is canonical Wire Diagram JSON your agents can edit. Source Sans 3 and Source Code Pro ship as self-hosted webfonts, the type scale is a real 1.250 ladder, and the masthead carries a contour-survey texture drawn entirely from tokens. Light and dark are both complete and both computed against WCAG AA.
sections and primitives
You get the parts, not just the demo site. Every frame is a real capture from the theme's own styleguide page, and the source path under it is where the file lands in your project.
docs-hero
src/components/docs-hero.tsx
The indexed masthead (archetype A9): version marker, headline, two actions, the first live request overhanging the container, and an eleven-entry index covering every route with the reader's own position marked
tokens, both modes
Change one variable and every part follows. Each badge is one token split down the middle: its light value on the left, its dark value on the right, with the theme's own paired ink on both halves.
hover or tab a badge for its name and both values, enter copies
every token
typefaces, self-hosted
Real woff2 files in src/fonts/, wired through next/font and licensed under OFL. Nothing is fetched from Google at build time, so the zip renders these letterforms offline. Scale ratio 1.25.
Meridian
A documentation theme built as a reading surface, with the four interactions a docs product is expected to have.
const { open, close } = useLedger("2026-03") // 0123456789
- text
- Source Sans 3
- mono
- Source Code Pro
No separate display face: the headings are set in the text face.
- d1Ag
- d2Ag
- d3Ag
- d4Ag
- leadAg
- bodyAg
- smallAg
- captionAg
- labelAg
- readAg
- scanAg
- codeAg
every width is a real render from the publish gate
Four viewports, each one a render the gate produced and checked. Switch between them: the frame narrows exactly as a window does, because that is what it is.
every token and every part on one page
The styleguide route is not documentation about the theme. It is a page in the zip that renders the real components from the real tokens, so it stays true the day you change one.
agent files in the zip
Unzip it and run it, or install it into a project you already have. Either way the theme arrives with the instructions an agent needs to extend it without guessing at your conventions.
- AGENTS.mdthe theme's own rules, written for an agent
- .claude/skills/4 skills
- add-pageCompose a new route for Meridian out of its existing sections and the three-pane frame, matching the shell, anchors and manifest entries of home/guides/api
- add-sectionAdd a new self-contained section to Meridian following its file, token and reading-surface patterns, then wire it into a page, the styleguide and the manifest
- check-qualityRun Meridian's own gate locally
- rebrandReskin Meridian for a buyer
- theme.jsontokens, pages and components, machine readable
- src/components/11 sections, 19 primitives
- src/app/8 pages, styleguide included
activity
- v2.1 — /changelog, /sdks, /support; every promised destination existstoday
- v2.0 — the reading edge, shipped faces, 1.250 ladder, A9 mastheadtoday
- v1.1 — contour luminance layer on the docs mastheadtoday
- v1.0 — three-pane docs, API reference, command-K searchtoday
- MDX content adapter exampleplanned
for agents
This listing is also a markdown document and a JSON endpoint. The theme's own agent files are on the plate above.
comments
Ask about the theme before you buy, or say what you did with it after.
