Project settings
The knobs that apply to a whole project.
// on this page
# General
This is a design example, so the words here are placeholder copy rather than real documentation. What's real is the terminal art direction: phosphor text on a near-black ground, monospace throughout, and the way each block type is styled.
Each step builds on the last. Where a real page would show output or a diagram, this example keeps a calm block of prose so the rhythm of the page can be evaluated on its own terms.
# Regions
A good docs page tells you what you're about to run and what you'll get back. A paragraph of roughly this length lets you judge the reading measure, the line height, and how body text sits between headings and code fences.
# install the CLI
$ npm i -g @neon/cli
# authenticate
$ neon login
→ opening browser…
✓ logged in as you@example.com
# deploy
$ neon deploy ./app
✓ build done in 4.2s
✓ upload 12 files
✓ live https://app.neon.sh# Build
Each step builds on the last. Where a real page would show output or a diagram, this example keeps a calm block of prose so the rhythm of the page can be evaluated on its own terms.
// NOTE
This page is part of a structure-only demo — the commands are illustrative placeholders.
# Danger zone
When you're done here, the on-this-page list and the prev / next links at the foot of the article carry you onward — the quiet machinery that makes a large manual feel navigable.
- -A clear title that says what the page is
- -A one-line summary underneath
- -Headings that map to the on-this-page list
- -Prev / next links to neighbouring pages