Skip to content
SleekSite AI Docs
On this page

Content modeling

Define the shape of your site's content: page and entry models, blocks, option sets, and the fields they hold.

Site Admins

A model is the shape of a piece of content: which fields a page, entry or block has, like a headline, a photo and a price. The forms in Content are built from models, and templates and the API read content by its field handles.

TipLet the AI Assistant do it. The easiest way to create or change models is to describe what you need: "Add a Team page with a photo, name, role and short bio for each person." The AI Assistant creates the model, the template and the page. Use the Models screen to fine-tune.

Block, Collection, StackBlock, Collection, StackReferenceDropdownPageModel+path+single or collectionEntryModel+handle+single or collectionBlockModel+reusable fields+no records of its ownOptionSet+label/value list

Four kinds of model#

Kind What it's for Example
Page Content with its own address /, /about, /blog/*
Entry Shared content with no address, shown on whichever pages need it Header, footer, testimonials
Block A reusable set of fields, used inside pages and entries The SEO fields on every page
Option set A shared list of choices for dropdown fields Allergens, categories

Pages and entries can each be single (one record, like the home page or the footer) or a collection (many records with the same fields, like blog posts or team members).

Page models#

Models: pages Pages Entries Blocks Options NEW PAGE 1 Home / 2 Menu /menu 3 /menu/* 4 /about 5 /catering 6 /visit 7 /contact 1 2 3 4 5
  1. Pages · Entries · Blocks · Options
  2. New page model
  3. Label and path; {..} = single page
  4. [..] = collection: many pages under one path
  5. Field count; expand to see the fields

When you create a page model, choose:

  • Label: its name in Content
  • Path: its address, like /about or /blog
  • Multiple records / Collection: turn on for many pages of the same kind. Each record gets its own slug, which completes its address: slug country-sourdough under /menu becomes /menu/country-sourdough
  • Admin only: hides this content from Editors completely
New page model New page Label Path / Multiple records / Collection Admin only CREATE 1 2 3 4
  1. Label shown in Content
  2. URL path (e.g. /blog)
  3. Collection: one page per record, each with a slug
  4. Hide this content from Editors

You can change all of these later, including switching a single page to a collection.

A model's fields#

Expand a model to see its fields, each with its type, handle and label.

Models: a page's fields Pages Entries Blocks Options NEW PAGE 6 /visit FIELD # Type Handle Label 1 Seo 2 text 3 text 4 5 6 Map 7 8 text 7 /contact 1 2 3 4 5 6
    • Field: add a field
  1. Edit code: open the template in Site Builder
  2. Edit model
  3. ⋮ → JSON to fields, Delete model
  4. Type · Handle (used in templates and the API) · Label
  5. Edit or delete a field
  • + Field: add a field
  • Code icon: open the model's template in Site Builder
  • Pencil: edit the model's label, path and settings
  • ⋮ → JSON to fields: add fields from sample data. ⋮ → Delete model removes it

Entry models#

Entries hold content that isn't a page of its own, like the header, the footer, FAQs or testimonials. Choose Single entry (one record, like the footer) or Multiple entries (a collection, like testimonials). Collection handles end in +, like testimonials+.

Models: entries Pages Entries Blocks Options NEW ENTRY 1 events+ 2 FAQs faqs+ 3 footer 4 header 5 testimonials+ 6 site-settings 1 2 3
  1. New entry model
  2. Single entry {..}: e.g. footer
  3. Collection [..]: handles end in +

Block models#

Blocks are reusable sets of fields, like seo. Define a block once, then use it in any page or entry with a Block, Collection or Stack field. Blocks have no records of their own: their content lives in the page or entry that uses them.

Models: blocks Pages Entries Blocks Options NEW BLOCK 1 Seo seo 2 Hero hero 3 columns 1 2
  1. New block model
  2. Used inside pages and entries (e.g. the SEO block)

Field types#

Text and values

Type Use for
Text Titles, names, short text. Turn on Multiline for a paragraph
Rich Text Formatted text, edited visually
Markdown Long text written in Markdown
Boolean Yes or no, like "show this banner"
Dropdown Options Pick one or more from a list, or from an option set
Color A colour picker
Date, Date Time Dates, or dates with times
Number Prices, quantities, order
Location A map location
Emoji A single emoji
JSON, Code Raw data, or CSS and JavaScript

Media and links

Type Use for
Image A photo or graphic, resized and optimised for each visitor
Video A video from your media library
File A document to download, like a PDF menu
Link A page on your site, or a web address
Reference Records from an entry collection, like picking testimonials to show on a page

Structure

Type Use for
Group Keep related fields together under one heading
Collection A repeating set of fields, like the items in a "Menu highlights" section
Block One block, like the SEO fields
Stack Editors choose which blocks to add, and in what order, while editing: flexible page sections
Data Table A spreadsheet-like grid
Select field type Select field type AI / YAML / JSON T Text R Rich Text M Markdown B Boolean D Dropdown Options C Color D Date D Date Time N Number J JSON C Code L Location R Reference I Image E Emoji V Video F File L Link D Data Table S Stack G Group C Collection B Block 1 2 3
  1. Create fields from JSON/YAML or with AI
  2. Reference: link to records of an entry collection
  3. Stack, Collection, Block: structured groups of fields

Creating fields quickly#

Choose AI / YAML / JSON when adding a field. Paste sample data, or describe what you need with Draft with AI, and the fields are created for you, with their types worked out from the data. For example, {"bg": "image"} creates an Image field called bg.

Create fields from JSON/YAML Create Model using JSON/YAML Add fields using sample JSON or YAML YAML JSON DRAFT WITH AI CREATE MODEL 1 2
  1. Draft with AI
  2. Sample data → fields (types inferred)

Field settings#

Field settings Update Title Field Field Label * Handle (Object key-name) * Multiline Multiple values? Validations Required Min Min Max 80 Type Reg Ex Field help UPDATE 1 2 3 4
  1. Handle: the key in templates and the API
  2. Type options
  3. Required, min/max length, RegEx
  4. Help shown to editors
  • Field label: what editors see. Handle: the key templates and the API use
  • Type options, like Multiline or Multiple values
  • Validations: Required, Min / Max and a RegEx pattern. These are checked when someone edits in the app, not on changes made through the API
  • Field help: a hint shown to editors under the field
  • Default value: pre-filled for new records. Pick GUID to give each record a unique ID

Option sets#

Option sets are shared lists of choices, each with a label and a value. Use them in Dropdown Options fields, so the same list appears everywhere, and in templates with getOptions('<handle>').

New option set New list List Name # Label Value 1 2 3 Nuts nuts Handle (optional) CREATE 1 2 3
  1. List name
  2. Label / Value rows
  3. Handle: getOptions('allergens') in templates and the API

Changing a model#

  • Renaming a field's handle keeps its content: content is stored against the field itself, not its name. Update any templates that use the old handle
  • Deleting a field deletes its content in every record
  • Switching a single page to a collection (or back) is done from the model's settings

WarningDeleting a field or a model can't be undone from the Models screen. If you delete something by mistake, restore an earlier version in Version history.

See Template & helper reference to use your models in templates, and Headless CMS to read content through the API.

Was this page helpful?

Last updated October 30, 2026