How it works

How the static pages API works

Every page is structured as sections and rows. Liquid templates control presentation. Exports package the final page for wherever it needs to live.

Start building View pricing
Workflow from reference page through structured content and Liquid templates to editable static HTML
Structured content, flexible output

Architecture

The content model

The system separates content, structure, and rendering so AI and people can collaborate safely.

Page

The route, SEO metadata, group settings, webhooks, and export mode.

Section

The major page bands: hero, benefits, FAQ, pricing, sliders, and custom layouts.

Row

The repeatable content inside sections, including cards, answers, images, links, and offers.

Template

Database Liquid, CSS, JS, field schemas, and sample data for reusable presentation.

Workflow from reference to export

Use default templates, clone them, or ask an AI to create custom database-backed Liquid templates.

Capture the reference

Capture the reference

Describe a page, paste a reference URL, or hand your AI a Figma mockup.

Create Liquid templates

Create Liquid templates

The AI writes Liquid, scoped CSS, field schemas, and sample data into database templates.

Edit normal content

Edit normal content

Users edit the page through the existing section and row forms instead of editing markup.

Export and publish

Export and publish

Export the rendered page and notify the destination system through webhooks.

1 / 4
Six-step static page workflow from captured reference to published destination

Technical FAQ

Implementation questions

These are the details teams usually need before connecting the API to a site.

Yes. Template JavaScript is rendered inline with the component so the exported HTML carries the behavior with it.

Yes. Group and page export settings can include the full head section or return only the body markup.

The template field schema declares editable inputs. The form renders those fields and saves instance values into template data.