Content Models

Content models define the structure of your content. They determine which fields an entry contains, how editors fill them in, and how that content is delivered through the API.

For example, a Blog Post model might include fields for a title, slug, summary, body, featured image, and publish date.

Create a content model

Create a content model before you start adding entries.

1. Go to Models → Content Models.
2. Click Create Content Model.
3. Enter a name for the model.
4. Review the generated API ID, if needed.
5. Save the model.

About API IDs

API IDs are generated automatically from the name. In most cases, you can keep the default value. Change it only if you want a different identifier for use in the API.

Add fields

Once the model has been created, add the fields editors will use when creating entries.

1. Open the content model.
2. Click Add Field.
3. Choose the field type.
4. Enter a field name and review the generated API ID, if needed.
5. Save your changes.

Choose field types based on the kind of data you need to store, such as text, rich content, references, assets, or reusable components.

Preview URL

In the Preview URL section, configure a full URL template so editors can open draft entries on your site from the entry editor toolbar. Use Copy from model to reuse a pattern from another type, then adjust the path. The token reference table lists built-in tokens, field tokens ({field.<apiId>}), and example values. See Preview Links for full details and frontend setup.

Organize fields with tabs

Tabs help keep larger models easier to navigate, especially when they contain a mix of editorial, technical, and supporting fields.

A common tab structure is:

• Content for the main editorial fields
• SEO for metadata and search settings
• Settings for flags, options, and other supporting values

For smaller models, tabs may not be necessary. For larger ones, they can make the editing experience much clearer.

Set the title field

Choose which field should represent the entry in lists, search results, and reference selectors.

In most cases, this should be a short text field such as Title.

A good title field makes entries easier to identify throughout the Studio, especially when editors are working with large volumes of content.

Next steps

• Field Types
• Taxonomies
• Components