Page Builder V4

Page Builder V4 is Antly’s Iris-first page authoring experience. Instead of dragging a component tree, you describe the page in natural language (or paste requirements), Iris writes a single default-exported React component, and you refine it in a studio with chat, preview, history, and an objects pane.

V4 pages still live on sites.Page with audience, roles, slug, settings, and history — only the content shape and editor differ from V3.

Studio layout

Pane	Purpose
Chat	Agent mode (edit page) and Ask mode (questions without mutating). Prompt queue for stacked refinements.
Preview	Live render of the compiled page against the shared React runtime
History	Prompt/page history; rewind or jump to earlier versions
Objects	Inspect object schemas while authoring data-driven pages

Empty pages start from a CTA that opens Iris generation. Saving writes sites.Page.content for version 4 and appends history.

Page kinds

Kind	Intent
Data-driven	Dashboards, object-backed admin views, filterable tables/charts
Website	Marketing/public pages with navigation, CTAs, and visual sections

Both kinds use the same runtime. Style guides (editorial, playful, minimal, brand-vibrant, and tenant settings) steer Iris generation.

Code rules (what Iris must emit)

One default-exported function component
No import statements — APIs are injected by the runtime
Use hooks for data (useJql, mutations, tables), Formik/Yup for forms, and special widgets for charts/reports/Iris chat
Prefer allowlisted images and style-guide tokens over arbitrary remote assets

Runtime capabilities

Capability	How
Data	`useJql` / mutation helpers against any allowed namespace
Tables	Table helpers with sorting/filtering
Filters	Page-level filter state + JQL `q` builders
Forms	Formik + Yup + Antly inputs; multipart via `PUT /jql`
Charts	`PageBuilderChart` backed by `reports.Chart`
Reports	`PageBuilderReport` download/export sections
Iris in-page	`PageBuilderIrisChat` with runtime-exposed topics
Context	`useRecordContext`, `useSearchParams`, auth context

Full API: Runtime overview, Data hooks, Widgets.

Audiences

Same as all Sites pages:

Audience	Typical URL
`public`	`/<slug>` — no portal chrome; ship your own nav
`authenticated`	`/sites/<slug>`
`admin`	`/admin/<slug>`

Optional allowed_roles further restricts access (failed checks look like 404).

Authoring workflow

Create a Sites page, set version 4, audience, and slug.
Choose a style guide in page settings if needed.
Open the studio and describe the page (layout, data sources, interactions).
Review the preview; queue follow-up prompts (“add a status filter”, “use objects.Case”).
Use Ask mode to inspect without changing code.
Save, preview as the target audience, pin to menu/launchpad if required.

Iris topics used while authoring

Authoring uses Iris V2 topics such as page-builder, page-builder-ask, and object-agent helpers. Runtime chat widgets only see topics marked expose to Page Builder runtime in Iris Studio. Details: Iris authoring contracts and Iris in Page Builder.