Content Entries
A content entry is one instance of a Model, filled with real data. A Page renders one entry, and a Flow Step can render one too.
What a content entry is
A content entry is an instance of the schema of a Model. The Model sets the fields, and the entry holds the values. One Model backs many entries, and each entry holds its own data.
The Model of an entry is fixed when you create the entry.
The entries list
CMS in the sidebar holds Content entries, with a count of every entry in the workspace.
| Column | What it shows |
|---|---|
| Title | The value of the first single-line text field of the entry. It falls back to the entry id when no such field holds a value. |
| Model | The Model that the entry belongs to. |
| Entry ID | The stable id of the entry. |
| Last updated | When somebody last saved the entry. |
The Model filter narrows the list to one Model. The list has no search, because the title is derived at read time and is not a column that Picked can search.
How entries bind to pages and steps
A Page has a single Step, and that Step links to its entry through the layout content link. A Flow Step with a Step Layout binds an entry the same way. When the SDK renders the Page or the Step, it resolves the linked entry and gives the data to your component.
Edit entry data
The entry editor renders a form from the schema of the Model. There is one input for each field, in the order that the schema sets. A repeatable field shows as a sortable list. You can add to that list and put it into a new order. A group field holds its inputs under one heading.
Reference fields
A Reference field holds a pointer at another entry, and not a copy of it.
| Control | What it does |
|---|---|
| Choose entry | Opens the entry picker. |
| Change entry | Opens the entry picker on a field that holds a target already. |
| Clear | Removes the pointer. It does not delete the entry. |
The entry picker lists the entries that the Target Model of the field allows, and it has a search box. Open model opens the Model of an entry in a new tab.
Validation
Invalid data shows as an error on each field. The error carries a path in the JSON style,
and it points at the exact place in the entry, for example sections[0].data.title.
A reference field reports an error when its target does not exist, or when the target belongs to the wrong Model. Fix every error before you publish, because Picked serves valid content only.
Delete rules
Picked does not delete an entry while something still points at it.
| Condition | Result |
|---|---|
| A Step uses the entry as its layout | The delete stops. |
| Another entry points at it through a Reference field | The delete stops. |
Clear the reference on the other entry first, then delete the target.
Related
- About the content model — why the schema and the data are separate.
- About content references — why a delete stops.
- How to create a content entry
- How to point one entry at another
- Models