Templates

What templates do

Templates are reusable Liquid-backed renderers for sections and rows. A template stores Liquid HTML, scoped CSS, optional JavaScript, sample data, default data, and a field schema that decides which custom values are editable.

Use templates when the built-in section or row renderer is not expressive enough, but you still want humans and AI to edit the content through structured fields instead of raw page-sized HTML.

Section templates and row templates

Templates target either Section or Row records.

• Section templates render full page bands and can receive section fields, template_data, and rendered child rows.
• Row templates render reusable child components such as cards, slides, FAQ items, metrics, badges, navigation links, or custom content items.
• If a Liquid-backed section expects child rows, prefer Liquid-backed row templates inside it so the section and rows share the same visual system.
• Built-in renderers use type_of. Liquid-backed renderers use template_id and template_data.

Default, Community, Examples, and My Templates

Default Templates are starter templates shipped with StaticPagesApi. Copy them into your organization before customizing.

Community Templates are templates published by other organizations. You can preview, like, and copy them into your own organization.

Examples are hard-coded starter patterns that can be opened as draft template forms or installed into My Templates.

My Templates are templates owned by your organization. These are the templates you can edit, duplicate, delete, or publish to the library.

How templates affect editing

A template-backed record stays editable through the normal section or row form. Standard fields such as title, body, images, status, order, classes, and styles still work when the template renders them.

Custom template fields are stored in template_data and are editable when declared in field_schema. Optional help_text and group metadata make their purpose clear in contextual section and row forms.