v0.1 demo shell

Demo of certificate design, preview, and authoritative render

This app is just a host shell. The actual design and render capability comes from @certificate/render-kit, which exposes a TypeScript authoring model, browser editor runtime, and server render surface while hiding the packaged WASM and CLI internals.

TypeScript-first IRBrowser and server start from the same document model.
Rust-owned fidelity10 resolved nodes through the packaged render stack.
Editor workflowSelection, CRUD operations, and preview stay inside the npm package.
Server deliveryAuthoritative PNG and PDF renders are spawned from the packaged CLI.

Browser editor + preview

Package-owned authoring flow over the browser runtime

The canvas, selection geometry, editing commands, and rerendering all go through @certificate/render-kit/browser. The app shell is only arranging the workspace and controls.

Status: idle

Canvas: 0 x 0

Selected: none

Server-side render

Spawn the authoritative PNG or PDF from the packaged CLI

This section exercises @certificate/render-kit/server on demand. The browser does not render these outputs. The package invokes the bundled Linux CLI, then the result is previewed here in-place.

Status: idle

Surface: PNG

Trigger a render to preview the server-produced output here.

Closing notes

What this v0.1 demo is intended to prove

The package can act as the rendering stack for a Node-capable full-stack web app without forcing the app to care about Rust artifacts directly. The browser gets a real editor surface. The server gets authoritative artifact generation. The surrounding product shell stays free to follow its own framework and UX choices.

This is intentionally honest about current scope:

  • The editor demo is package-driven, but still a small curated surface.
  • The server section proves packaged CLI invocation and in-page artifact preview.
  • The UI shell is framework-specific only at the host-app layer.
  • The renderer itself remains an independent infrastructure boundary.