Blueprint x Theme Playground

Choose a blueprint, switch a safe theme, inspect the request.

This Phase 1 playground is a static rendered sample experience. It uses pre-rendered HTML/PDF evidence assets and client-side JSON validation only; it does not call the main API, ask for an API key, upload files, or accept arbitrary HTML, CSS, XML, or scripts.

Payload

Client-side JSON editor

Validation

Static safety checks

    Request shape

    Preview request body

    Use this body with POST /api/whiteLabelEngine/v1/render/preview after beta access. This page does not send it.

    Preview

    Static rendered sample

    Changing the JSON validates the request shape and updates the snippet. The visual pane remains a pre-rendered evidence asset until a separate sandbox preview endpoint exists.

    Trust boundary

    What this playground will not do

    • No network call to the main authenticated API.
    • No API key field, file upload, remote image fetch, arbitrary layout code, or database connection string.
    • No claim of browser-perfect CSS control, regulatory compliance, or byte-for-byte PDF proof for edited anonymous payloads.
    • No durable persistence of submitted payloads or rendered outputs.

    Phase 1 is static by design

    The page uses the same public assets as the gallery: template-gallery/index.html, template-design-comparison/index.html, PDF outputs, HTML previews, render manifests, and fictional sample payloads. It gives visitors the immediate blueprint/theme aha moment while keeping teleza.tech on static files only. A bot can request the page repeatedly without triggering anonymous PDF compilation work on the VPS.

    Phase 2 remains a backend milestone

    A live sandbox should use an isolated low-privilege endpoint such as POST /api/public/preview-sandbox, not the main authenticated API. The risk is denial-of-wallet render load against the same infrastructure serving private-beta partners. Phase 2 must include a 50KB request cap, Caddy or edge rate limits, Turnstile-style human challenge, strict schema and nesting limits, allowlisted templates and themes, small row limits, secret and PII rejection, roughly 1.5 second timeout budgets, output caps, sanitized telemetry, and no durable persistence of submitted payloads or rendered outputs.