Members & access

# Roles

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.

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.

# Adding members

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.

# 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

# Tokens

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.

# SSO

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.

• -Run `neon login` to authenticate
• -Run `neon init` in your project
• -Commit the generated `neon.toml`
• -Run `neon deploy` to ship