Live custom-component proof
Estimate a monthly mortgage payment
Change the example assumptions to see principal, interest, property tax, insurance, and HOA dues update in the browser. The inputs stay on this device and are never submitted.
What this route proves
A unique interaction can remain a first-class Sights component.
The calculator is implemented inside this consumer, not the reusable platform. Its trusted TypeScript definition registers a strict props schema, authoring guidance, accessibility requirements, examples, semantic thumbnail, Astro renderer, and one client-runtime path.
Sights generates its schema and catalog entry, renders its component viewer example, validates every page use, and loads the runtime only on routes that select the calculator.
- Server-rendered baselineThe initial result, field values, labels, explanation, and disclaimer exist before client code runs.
- Accessible updateInput labels persist and the recalculated total is announced through a polite live region.
- Runtime isolationThe calculator module is present here and absent from the product homepage and ordinary content routes.
The full extension contract
See how custom components stay inside the system.
The extensibility page covers schema design, trusted code, examples, generated documentation, primitives, runtime declarations, and promotion into the shared platform.