studio-engineBuilderEmail EngineFolio

Showcases

Each surface runs against the repository’s committed fixtures. Nothing here is a recording or a mock — what a page shows is what the code did when the page asked it.

  • Builder

    The email editor, mounted over the real asset-pipeline fixture corpus.

    One props surface: pick a fixture and the whole session re-opens on it. Every edit crosses the same seam a product would use — the host stores no documents of its own.

  • Email Engine

    Seven stages from a Figma asset to delivered email HTML, run one sample at a time.

    Pick a sample, run it, and watch each stage report its own verdict and artifacts. The stages run in the API over the committed corpus — nothing here is a recording.

  • Folio

    Every asset the capture pipeline has written, read straight out of the store.

    Three tables kept apart on purpose: an identity, the versions whose bytes never change under their URL, and the pointer saying which version an environment serves. Nothing is seeded — an empty store shows as empty.