PLIEGORS / DOCUMENTATION
Build the whole document in Rust.
Start with useful HTML, add state that can explain itself, and admit browser libraries only through explicit lifecycle boundaries.
START / 04 COMMANDS
From zero to a running project.
The default starter is intentionally small, but it is not blank: it teaches the route graph, authored errors, metadata, assets, and the build ledger.
pliego new my-app
cd my-app
pliego check
pliego devStart
Getting started
Install the CLI, create a project, start the development server, and produce the first verified build.
↗02Start
Project structure
Understand pliego.toml, the site package, the optional WASM client, public assets, and output ownership.
↗03Start
CLI reference
Use new, check, build, dev, preview, inspect, templates, and machine-readable diagnostics.
↗04Start
Developer loop
Follow native file events through typed HMR, causal build graphs, artifact explanations, and recovery without losing the last valid output.
↗05Author
Routing and pages
Create complete HTML documents, canonical metadata, clean routes, redirects, and authored error pages.
↗06Author
Rust views
Compose semantic views with escaped text, typed macros, stable attributes, and useful HTML first.
↗07State
Events and folds
Model durable facts, deterministic projections, replay parity, snapshots, and explicit effects.
↗08State
Schemas and snapshots
Version events, seal adjacent upcasters, bind projection identity, and restore snapshots only against an exact compatible contract.
↗09State
Hyphae verified sync
Append and replay durable history through signed attestations, fixed snapshots, authority policy, and consuming verification types.
↗10Author
Typed content
Load bounded Markdown, JSON, and TOML collections with stable identities and actionable errors.
↗11Runtime
Browser runtime
Resume Rust/WASM behavior and admit GSAP, Lenis, Three.js, or WebGL through lifecycle adapters.
↗12Runtime
DOM ownership
Own mounted ranges, reconcile keyed children, adopt exact SSR output, and dispose listeners, effects, adapters, and nodes deterministically.
↗13Delivery
Adaptive assets
Plan reproducible images, video, fonts, and 3D variants under explicit device budgets.
↗14Delivery
Artifact trust
Understand portable namespaces, exact source capture, staged publication, build receipts, causal graphs, and fail-closed verification.
↗15Operate
Errors and diagnostics
Read stable PLG codes, browser build failures, JSON diagnostics, exit codes, and recovery actions.
↗16Delivery
Build and deploy
Verify the output ledger, preview production bytes, select release artifacts, and deploy static output.
↗17Reference
Crates and API
Choose the public crate that owns each contract, generate exact-version Rustdoc, and avoid depending on implementation-only internals.
↗18Project
Licensing and policy
Understand Apache-2.0, third-party notices, trademarks, security reports, support, and contributions.
↗