This entire product site is authored, validated, and rendered with Sights.See how it works
Menu

Interactive tools

Add the useful interaction. Keep the rest of the site a website.

Calculators, estimators, filters, and guided tools can live inside a Sights consumer as site-owned components. Their schemas, fallback, runtime, docs, examples, and tests remain isolated to the capability.

Try the calculator proof
An interactive mortgage calculator with inputs, a live result, and a transparent breakdown

Focused browser capabilities

Use custom interaction when it helps a visitor make sense of information.

  • Calculators

    Turn a set of visible assumptions into an immediate estimate or breakdown without transmitting visitor data.

  • Estimators

    Help readers understand ranges, scenarios, or inputs while keeping disclaimers and calculation boundaries visible.

  • Guided selectors

    Narrow a known set of options using local state and accessible controls without requiring an account or server session.

  • Search and filters

    Improve navigation through a bounded local catalog when static index pages alone are not enough.

  • Comparative tools

    Let readers change approved inputs while the component owns consistent output semantics and explanation.

  • Progressive widgets

    Enhance a useful server-rendered baseline instead of hiding the entire outcome behind client startup.

Runtime contract

Interaction crosses a visible boundary.

  1. Render a useful baseline

    Astro produces the component's complete initial structure, labels, explanatory copy, and initial result.

  2. Load one declared module

    Only routes using the component receive its root-relative client runtime.

  3. Scope state to the component

    Client code binds inside the component boundary instead of becoming a site-wide application shell.

  4. Keep data local by default

    The current calculator performs all work in the browser and sends no visitor inputs anywhere.

  5. Test isolation

    The browser gate verifies both the live interaction and the absence of the custom runtime from unrelated pages.

A deliberate limit

An island is not permission to smuggle in an application platform.

A focused custom component fits when the page remains understandable as a document and browser state supports one bounded task.

Authenticated dashboards, multi-user state, real-time collaboration, durable user data, and application-wide navigation are better served by a product framework designed for those responsibilities.

  • Good boundaryOne calculator, selector, filter, estimator, or visualizer with a strict local contract.
  • Warning signThe component needs global application state, accounts, arbitrary server routes, or durable personalized storage.
  • Honest choiceKeep the marketing and content site in Sights and link to a separate application when the product boundary is real.

Live product proof

Try the site-owned calculator and watch the boundary hold.

Its result updates in the browser, its component contract appears in generated docs, and its client module stays off every unrelated route.

Open the mortgage calculator