Collections

A collection defines the shape of one kind of content - a Blog Posts collection, a Products collection - as a named set of typed fields. Every entry created against a collection shares that same field structure.

Creating a collection

1. From a project, open Collections and choose New Collection.
2. Give it a display name and a slug - the URL-safe identifier used in the Content API's routes (/collections/:slug/content) and never shown to editors.
3. Add fields one at a time, choosing a field type for each.

Entries and drafts

Once a collection has fields, editors create content entries against it. Each entry can be saved as a draft and published independently, and the Content API's state parameter controls whether drafts are included in a response (see Parameters).

Changing a collection later

Fields can be added, reordered, or removed after a collection is in use. Removing a field does not delete the values already stored against existing entries for other fields, but any data held in the removed field itself is no longer reachable.