Add a Get started section with an end-to-end quickstart

[andrewleesteele]

Summary

The docs have no code-along path. The home page is a landing page, and each guide covers one stage in isolation — so there's nowhere to send someone who just wants to get a browser running and then take it to production.

This adds a Quickstart in a new Get started nav group: install and authenticate → create and drive a browser → watch it → pointers for stealth/proxies/auth → serve a workload from a browser pool.

Browser pools are the last stage of this guide rather than a quickstart of their own, so the walkthrough lives here and /browsers/pools stays reference-only. Its "Full example" moves into this guide, and the pools page gets a short pointer back.

Also drops the stale /quickstart → / redirect, left over from when an earlier quickstart was folded into the home page — without removing it, the new page would be shadowed. The home page's "start here" now links into the guide.

Content notes

• The browser-pool stage ends with the three things that actually bite in production: always release in a finally (an unreleased browser stays acquired until timeout and the pool drains), reuse: true hands the same browser — cookies and logins included — to the next caller, and idle pooled browsers aren't billed but their capacity still counts against the concurrency limit.
• CLI and SDK details are taken from the existing CLI reference rather than invented: brew install kernel/tap/kernel / npm install -g @onkernel/cli, kernel login, kernel api-keys create, and KERNEL_API_KEY for the SDKs.
• Nav: Get started sits below Overview, so the sidebar still leads with Introduction.

Base branch

This is stacked on hypeship/browser-pools-docs-refresh (#464) rather than main, because the pools-page edits here depend on that branch renaming browsers/pools/overview.mdx → browsers/pools.mdx. Merge #464 first, then this. Its diff shows only the quickstart changes.

Verification

• docs.json is valid JSON; every nav entry resolves to a file; quickstart is in the nav; no stale /quickstart redirect remains.
• Code fences and MDX tags balance in quickstart.mdx; all internal links and Card hrefs resolve, including /browsers/pools#sizing-a-browser-pool.
• Pools page still balances its fences/tags after the Full example was removed, and no references to it remain.
• mint dev not booted in this environment, so the page isn't visually confirmed — worth a preview pass.

Needs a human call

#278 ("Redesign quickstart with agent-first one-command approach") also creates quickstart.mdx. I left it untouched. Close it, or fold its one-command approach into this guide before merge — the home page already carries a copy-prompt setup box that covers similar ground.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Error		Jul 30, 2026 5:09pm

[cursor]

Risk assessment: Very Low

Verdict: Very Low risk — approved.

Evidence (from diff only)

File	Change
quickstart.mdx	New Mintlify docs page (end-to-end install → browser → pools walkthrough with TS/Python examples)
docs.json	Adds Get started nav group; removes /quickstart → / redirect so the new page is reachable
index.mdx	Adds a link to /quickstart
browsers/pools.mdx	Adds an Info callout pointing readers to the quickstart

Why Very Low

• Documentation-only on a Mintlify docs site — no application code, APIs, auth, billing, infra, or runtime logic.
• Small, scoped surface: one new guide page plus navigation/cross-link wiring.
• No shared libraries, schemas, deployments, or security boundaries touched.
• No CODEOWNERS file requiring human ownership review.

Action

Approved per Very Low risk criteria. No reviewers assigned.

  

_{Sent by Cursor Automation: Assign PR reviewers}