# Mintlify — DESIGN.md

> knowledge currents x docs console

**Aesthetic:** Data-as-Texture · **Mode:** persuade · **Color strategy:** restrained · **Focus:** hero  
**Reference:** https://www.mintlify.com/ (captured 2026-09-18)

Match the feel of this reference, not its content. Hexes and measurements are sampled from the page; type character, materials, and direction are interpreted from screenshots.

A white documentation platform makes infrastructure visible as bundles of green signal lines flowing behind a serif claim and into a large, lightly tinted documentation console.

## Colors

| Hex | Role |
|---|---|
| `#fefdfb` | page ground |
| `#121715` | primary ink |
| `#0c8c5e` | interface accent |
| `#7df43b` | signal line highlight |
| `#e9f7f1` | product panel tint |
| `#485450` | secondary ink |

## Typography

- **Display:** Arizona Flare serif at ~62px regular, left-aligned, three compact lines
- **Body:** Inter at ~20px regular with selected nouns in semibold
- **Labels:** Paper Mono for traffic readouts; Inter medium for navigation and buttons

## Materials

- white screen ground
- bundled vector signal lines
- mint-tinted docs panels
- fine interface borders
- mono traffic readouts
- line-art feature tiles

## Signature details

- white infrastructure ground
- green signal line bundles
- serif knowledge headline
- agent traffic readout
- oversized docs console
- mint grid illustrations
- modular product tile system

## Direction

### THESIS

knowledge infrastructure is a current that continuously feeds products and agents; the signal lines are the architecture. It refuses the static documentation screenshot floating in empty space.

### OWN-WORLD

a warm white #fefdfb field, near-black #121715 ink, forest green #0c8c5e controls, and many hairline currents shifting from mint through acid green. Use Arizona Flare for the central claim, Inter for explanation and controls, and Paper Mono for live metrics. Product surfaces are thin-bordered white panels with pale mint tile wells and tiny line-art objects.

### STORY

the visitor sees the infrastructure promise, watches the docs console receive the signal, then follows the current through knowledge access, system connections, scale proof, customer stories, and updates.

### FIRST VIEWPORT

place a slim report banner above a spacious nav. Left-align a small traffic readout, a three-line serif headline, a two-line lead, and two actions. Fill the right half with an oversized documentation console cropped by the viewport. Route two bundles of green lines diagonally behind it—one descending from the upper right, one rising from the lower left—so the console appears connected rather than floating.

### FORM

a network diagram flowing through a documentation workspace. Motion: not observed; if used, move a few line pulses along fixed paths while keeping panels still.

## Avoid

- Do not let decorative data claim things the product cannot show; texture, not evidence.
