Controlling the models that appear in the content tab for editors.
Stackbit automatically determines how to handle the models that appear in the content tab in the visual editor.
These are broken down into two categories of models:
How models appear in each of these tabs depends on the content source. Learn more about model types.
When working with file-based content (Git CMS) and most API CMSs (e.g. Contentful, you have to tell Stackbit which models are pages. These are the models Stackbit shows in the pages section of the content tab.
Data models are generally meant to be those which are accessed globally (e.g. a model with global header data), or referenced within a page model (e.g. an
Author model by be referenced by a
Git CMS Data Models
When using files as the content source, you are required to model all content explicitly, specifying the appropriate
type for each model.
Because of this, Stackbit knows which models are of the
data type, and that's what is shown in this section.
API CMS Data Models
Most API CMSs have a more open concept of model types, and Stackbit has to take a more conservative approach on what to show in the data models section.
Here are specific notes about supported CMSs:
- Contentful: Every model in Contentful produces entries. When configuring Stackbit, you would specify those entry models which are of the
pagetype. All other models are assumed to be of the
datatype and are shown in the tab. This is why you may see components and other models that are typically considered
- Sanity: Sanity has two types of models — document and object. When configuring Stackbit to work with Sanity, you would specify which document models are of type
page. All other documents are assumed to be of the
datatype and are shown in the data section. Objects are not shown anywhere in the content tab.