Reference
Look up the exact contract of the pinned V2 engine, then follow the task guide when an operation needs a sequence. This section separates source behavior from the external services and operating practices you must supply. V2 is the project name; the pinned package reports 1.1.4 and requires Node.js 24 or newer.
Choose the reference
| Need | Open |
|---|---|
| Scripts and builder flags | Commands |
| Process settings and parsing | Environment variables |
| Files, stores and recovery | Storage and formats |
| Pipeline and source modules | Architecture and contributing |
| Built-in feature boundaries | Capabilities and limits |
| A failed task | Troubleshooting and support |
| Evidence and open test gaps | Validation limits |
| Existing first-generation links | Old URL map |
The command page includes input flags and destructive output boundaries. Environment settings belong to particular processes; a reader preview setting is not an editor setting. Storage identifies what is source, generated output, private server state or browser-only recovery. Read these together before changing paths or service configuration.
Keep the layers distinct
| Layer | Contract |
|---|---|
| Source | Markdown, configuration and assets |
| Build | Generated HTML, assets and search |
| Reader | Browser interaction with static files |
| Editor | Optional private writing process |
| Publish | Local staged output switch |
| Hosting | External delivery and reader access |
A successful Save does not build pages. A successful Publish does not commit to Git or deploy a remote site. Hidden navigation does not remove content from output or search. Editor section assignments restrict writing, not public reader access. Save, publish and deploy follows those boundaries through one change.
Read evidence at its actual scope
Source inspection explains the pinned implementation. Tests exercise their fixtures and assertions. Local browser checks show behavior in the inspected browser and state. Neither establishes your production TLS, DNS, proxy, audience, capacity or recovery readiness.
The handbook uses tables for comparable options and exact contracts, but a table is not a new guarantee. For infrastructure templates, follow the installation guide and rehearse on your real system. For a bug, retain the first failed stage and a small safe reproduction instead of treating repeated clicks as a diagnostic method.
Change safely
Inspect the actual paths and runtime before a command. Keep source and private data away from cleared output folders. Preserve unsaved text before refreshing a failed editor. Review generated pages and search after changes, then check the deployed artifact separately. If an internal title changes, inspect the real route and update old links deliberately; V2 does not create automatic redirects.
Complete setup is the installation path. Run covers operations. Use covers writing and reading. Examples provides inspectable specimens rather than assumed production deployments.