Support · Fictional demonstration

From specimen to service

The boundary between static publishing, local interaction, and server-backed capabilities.

Every example renders its content at build time. Search, gallery enlargement, collection filtering, pagination, and application state use progressive browser JavaScript. No external libraries or remote APIs are required.

Connect these deliberately
CapabilityRequired integrationDemo behaviour
Contact / newsletterSubmission endpoint, consent, delivery, abuse controlsLocal validation only; nothing sent
Accounts / 2FAIdentity provider, sessions, server verificationNo credentials accepted by a server
Payments / bookingsPayment or registration provider and confirmed statusLinks to an example enquiry
MessagingAuthorised messaging service and delivery acknowledgementsMessages exist only in page memory
Sensors / fleet / VRAuthorised device/data adapter or rendererSimulated data or static scene
HTTP errorsHosting-specific error routing and status configuration404 file supplied; 500 specimen is a normal static page

The shared JSON catalog has no Liquid, JSX, or theme classes. Astro and React adapters should implement its section roles, URL handling, accessible states, and capability boundaries. See the downloadable source documentation for the schema and acceptance checklist.

A integration guide recipe in Krigsvold. Capabilities and integration boundaries · All examples