title,
slug, icon, description, and a type that determines how it renders and what
configuration it requires. This page covers the list and visualization types; the
detail and creation experiences (Single Record and New Record) are on the
Single Record pages page.
Shared configuration
A few rules apply across the types below:- Field references — a layout page refers to a section field by its slug.
- Template fields — text fields like
title,subtitle, anddescriptionaccept a mix of free text and{{field_slug}}references, so you can compose a label such as{{given_name}} — {{status}}. A template field must contain either text or at least one valid field reference. - Attribute validation — fields referenced by a layout page must exist as attributes on the section’s object type (or as fields on its View).
Aggregations
Several types support aggregations — summarized values such as a count or a total. Each aggregation names a function, the field to aggregate, and a label:| Function | Computes |
|---|---|
count | Number of records. |
count_unique | Number of distinct values. |
sum | Total of a numeric field. |
average | Mean of a numeric field. |
min / max | Smallest / largest value. |
earliest / latest | Oldest / newest date. |
Data Table
A tabular list with sorting, filtering, and pagination.| Configuration | Required | Description |
|---|---|---|
| Columns | Yes | At least one column. Each column declares its field slug, data type, and appearance; slugs must be unique and must exist as attributes. |
Kanban
Cards grouped into columns by the steps of a Workflow.| Configuration | Required | Description |
|---|---|---|
workflow_id | Yes | The Workflow whose steps become the columns. It must exist and have at least one step. |
title, subtitle, description | Yes | Template fields for each card. |
tag, date, slug, rating, like_dislike, toggle_switch | No | Optional field slugs shown on the card. |
| Aggregations | No | Per-column totals — see Aggregations. |
Calendar
Records placed on a calendar by a date field.| Configuration | Required | Description |
|---|---|---|
datetime | Yes | The date field that positions each record. Must exist as an attribute. |
title | Yes | Template field for each entry. |
color_field_slug | No | A field used to color entries. |
Timeline
Records drawn as spans between a start and an end date.| Configuration | Required | Description |
|---|---|---|
start_datetime, end_datetime | Yes | The fields that bound each span. Must exist as attributes. |
title | Yes | Template field for each span. |
color_field_slug | No | A field used to color spans. |
Map
Records plotted on a map by a location field.| Configuration | Required | Description |
|---|---|---|
location_field | Yes | The location field that places each record. Must exist as an attribute. |
title, subtitle, description | Yes | Template fields for each marker. |
image, default_image | No | A field for a marker image, and a fallback image. |
color_field_slug | No | A field used to color markers. |
tag, date, slug, rating, like_dislike, toggle_switch | No | Optional field slugs shown on the marker. |
Cards Grid
Records shown as a grid of cards.| Configuration | Required | Description |
|---|---|---|
image | Yes | The field used for each card’s image. |
title, subtitle, description | Yes | Template fields for each card. |
default_image | No | A fallback image when a record has none. |
tag, date, slug, rating, like_dislike, toggle_switch | No | Optional field slugs shown on the card. |
Front Page
A dashboard-style home for the section. The configuration is free-form — there’s no fixed schema — so you compose widgets and summaries to fit the section.Funnel Report
A funnel-analytics view. It takes no per-page configuration; its data is driven by the Engagement Funnels the app references.Related
Sections
The data unit that holds layout pages.
Single Record pages
The detail view and the New Record form.
Workflows
The steps that drive a kanban board’s columns.
Attributes
The fields a layout page references.