Model your content with schemas
Design content schemas in Stratafold: the twelve field types, validation rules, slugs, references and which fields the AI can write.
For owners and admins. 7 minute read. Updated .
A content schema is the shape of an entry: the fields an editor fills in and the JSON your website receives. Good schemas describe what the content is, not how a page looks, so the same entry can appear on your website, in an app or in a newsletter.
Only owners and admins can create or change schemas. Editors can see them.
Create a schema
Open Content schemas → New schema. Give it a Name such as Case study. Stratafold suggests an API ID (case_study), which is used in delivery API URLs and can’t be changed later. Then choose Add field for each piece of content.
Entry title comes from decides which text field names each entry in lists. Pick the field people recognise entries by, usually Title.
Field types
| Type | Use it for | AI can write it |
|---|---|---|
| Text | Titles, names, short or multi-line plain text | Yes |
| Rich text | Articles and long descriptions, written in Markdown | Yes |
| Number | Prices, ratings, quantities | Yes |
| Boolean | Yes/no switches such as Featured | Yes |
| Date | Event dates, with or without a time | Yes |
| Select | One or several values from a fixed list | Yes |
| Slug | The URL segment for the entry | Yes |
| Tags | A list of short keywords | Yes |
| Image | An image URL with alt text and caption | No |
| URL | A link to another page or site | No |
| A contact address | No | |
| Reference | Links to other entries in the workspace | No |
Images, links, emails and references always come from people. They point at real things, so the AI never invents them.
Validation that protects your website
Each field can be Required to publish. Drafts can be saved half-finished, but an entry can’t be published until its required fields are filled. Text fields can have a minimum and maximum length and can be marked unique across entries. Number fields can have a range or accept whole numbers only.
Slugs are always unique within a schema. If a slug is generated from the title and already taken, Stratafold adds -2, -3 and so on. A slug you type yourself that clashes is flagged so you can choose another.
Guiding the AI per field
Every AI-capable field has an AI writes this field switch. Turn it off for fields that must be written by a person, like a legal disclaimer. Use Instructions for the AI for field-specific rules: “One sentence that makes the reader want to click” for an excerpt, or “Three to five bullet points” for a features field.
Changing a schema later
You can add, reorder and remove fields at any time. The API ID of an existing field is locked, because entries store their values under it. Removing a field hides its stored values from editors and the API. Every change increases the schema’s version, and if two admins edit the same schema at once, the second save is refused instead of silently overwriting the first.
References between entries
A reference field links one entry to another, such as a Case study to its Client. You can limit which schemas it may link to and allow one or several links. The delivery API can return referenced entries inline with include=1.