Quickstart
Scaffold a Vango app, run the dev server, and understand the basic directory layout.
Programming Model
Understand Setup, render purity, Resources, Actions, and the session loop.
Components & State
Signals, memos, Resources, Actions, identity, and persisted state surfaces.
Routing & User Flows
File-based routes, layouts, typed params, navigation, page actions, and forms.
Architecture
A curated entry into the internal architecture docs and subsystem map.
Documentation Runtime
How vango-docs mounts markdown, search, code tabs, and AI-friendly copy output.
Release Notes
Current release notes and migration notes sourced from the Vango repo.
Core Concepts
Server-owned UI state
Vango keeps authoritative UI state on the server. The browser is a render target, not the source of truth.
The session loop is the writer
Reactive writes stay on the session loop, which keeps ownership and update flow explicit.
Setup allocates, render computes
State is allocated in `vango.Setup`, and render closures stay pure and deterministic.
Resources and Actions own blocking work
Async reads and mutations live in the right places instead of leaking into render paths or event handlers.
Client boundaries are explicit
Hooks, islands, and WASM exist, but Vango expects you to pick the smallest capability that fits.
Deploy safety is part of the framework
Generated routes, bindings, state artifacts, and warm/cold deploy planning make persistence changes visible before rollout.
This docs site is curated
These pages are curated summaries built from the Vango README, the Developer Guide, architecture docs, release notes, and `vango-docs` package guide. When you need full detail, each page points back to the deeper source material in the Vango repo.