Content Editor
Traditional CMS form-based editing, with the ability to edit content within page and data models.
The content editor is a way to quickly edit structured pages and data objects. This is similar to traditional form-based editing within a CMS.
The editor distinguishes between models (content types, collections, etc.) that represent pages and those that may globally affect any page on the site.
Filtering Documents
Various filtering methods make it easier to pinpoint specific documents (entries, items, etc.) within the available models.
Searching
Using the search field will look into all documents and return results for that document.
At the model level, Stackbit will only show models with a document that matched the search query, along with a count of the number of matched documents. Searching will also look to match the name of the model.
Within a model, searching filters the list of visible documents based on the query.
Field Filters
It is possible to filter content entries both by metadata (e.g. the shared createdAt
property or by individual fields, including references (e.g. posts with a specific author).
Filter Control
Field filters are controlled by the filter icon next to the search input.
Add as many filters as necessary to pinpoint the right subset of content.
Available Field Controls
The available fields change context based on documents available in the current view. When viewing a models list, Stackbit metadata fields will be available (createdAt
, updatedAt
).
When viewing documents within a model, fields for that model will be shown.
Filtering References
When filtering by referenced objects, you’ll be prompted to select existing content entries. Opening the select dropdown will trigger a modal from which you can choose the appropriate entry.
After choosing the appropriate document(s) and clicking Select, the selected documents will appear in the filter control.
Visible Models
Stackbit shows page and data models in the content tab, determined by the type
property set on the model.
Getting models to appear in the pages section often requires using the modelExtensions
configuration property to set the type
property for page models.
Content Source Exceptions
Some content sources have specific behavior on how models are inferred by Stackbit. Refer to content source integrations for more information.