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.

PLIEGORS / 0.4.0-BETA.1 / 21 CRATES

One coordinated public beta.

The CLI and all twenty library crates are published on crates.io at the exact 0.4.0-beta.1 version, including pliego-router, pliego-runtime, pliego-data, pliego-pboc, pliego-cloudflare, and pliego-sdk. G1, G2, G3, and OpenSDK move as one graph; PBOC v1alpha1 remains a preview contract.

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.

shell
pliego new my-app
cd my-app
pliego check
pliego dev
01

Start

Getting started

Install the CLI, create a project, start the development server, and produce the first verified build.

02

Start

Project structure

Understand pliego.toml, the site package, the optional WASM client, public assets, and output ownership.

03

Start

CLI reference

Use the project, diagnostics, upgrade, release-inspection, and voluntary telemetry command surfaces.

04

Start

Developer loop

Follow native file events through typed HMR, causal build graphs, artifact explanations, and recovery without losing the last valid output.

05

Start

Incremental builds

Use verified no-ops, explicit lazy-route dependencies, observable reuse, and private cache controls without weakening atomic publication.

06

Author

Routing and pages

Create complete HTML documents, canonical metadata, clean routes, redirects, and authored error pages.

07

Author

Rust views

Compose semantic views with escaped text, typed macros, stable attributes, and useful HTML first.

08

State

Events and folds

Model durable facts, deterministic projections, replay parity, snapshots, and explicit effects.

09

State

Schemas and snapshots

Version events, seal adjacent upcasters, bind projection identity, and restore snapshots only against an exact compatible contract.

10

State

Hyphae verified sync

Append and replay durable history through signed attestations, fixed snapshots, authority policy, and consuming verification types.

11

Author

Typed content

Load bounded Markdown, JSON, and TOML collections with stable identities and actionable errors.

12

Runtime

Browser runtime

Resume Rust/WASM behavior and admit GSAP, Lenis, Three.js, or WebGL through lifecycle adapters.

13

Runtime

DOM ownership

Own mounted ranges, reconcile keyed children, adopt exact SSR output, and dispose listeners, effects, adapters, and nodes deterministically.

14

Runtime

Native runtime preview

Install the public G1 router and runtime preview, then evaluate HTTP/2, route-owned layouts, bounded lifecycle, and three SSR modes.

15

Delivery

Portable deployment

Validate one sealed PBOC, admit native or Cloudflare hosts, and prove rolling and rollback compatibility before upload.

16

Runtime

Full-stack beta

Use the published G2 loaders, progressive actions, sessions, cache isolation, invalidation, and receipt-driven diagnostics.

17

OpenSDK

OpenSDK preview

Install the public OpenSDK preview and understand admission, capabilities, effects, conformance, and its pending governance.

18

OpenSDK

Components and languages

Run the typed Wasm Component host and compare the bounded Rust, TypeScript, and Python conformance implementations.

19

OpenSDK

Browser framework conformance

Integrate React, Svelte, and Lit through explicit Custom Element and adapter lifecycles with measurable cleanup.

20

OpenSDK

Tooling protocol

Negotiate editor and MCP clients over bounded JSON-RPC without granting ambient project or network authority.

21

OpenSDK

Compatibility and deprecation

Read the machine-verifiable support matrix, stability tiers, migration requirements, and provider-neutral source boundary.

22

Delivery

Adaptive assets

Plan reproducible images, video, fonts, and 3D variants under explicit device budgets.

23

Delivery

Artifact trust

Understand portable namespaces, exact source capture, staged publication, build receipts, causal graphs, and fail-closed verification.

24

Delivery

Release trust

Verify deterministic archives, signatures, attestations, provenance, and release-only promotion evidence.

25

Operate

Performance evidence

Reproduce benchmark observations, read their hardware context, and keep measurements separate from claims.

26

Operate

Errors and diagnostics

Read stable PLG codes, browser build failures, JSON diagnostics, exit codes, and recovery actions.

27

Operate

Voluntary telemetry

Control a disabled-by-default, local-only usage journal with an exact field allowlist and user-owned deletion.

28

Delivery

Build and deploy

Verify the output ledger, preview production bytes, select release artifacts, and deploy static output.

29

Reference

Crates and API

Choose the public crate that owns each contract, generate exact-version Rustdoc, and avoid depending on implementation-only internals.

30

Project

Licensing and policy

Understand Apache-2.0, third-party notices, trademarks, security reports, support, and contributions.