Structure content with collections and fields
Create a reusable content structure for articles, people, products, locations, and other repeated information.
Start with the content you repeat
A collection groups items that share the same fields. An Articles collection might have a title, summary, cover image, body, and author. A Team collection might have a name, role, photo, and biography. Each article or team member is an item in its collection.
Collections organize content; pages determine how visitors see it. Creating a collection does not automatically provide every item with a public page. You can later use its items in a list, cards, a filter, or a shared detail-page design.
Create a collection
- Open CMS and choose New collection.
- Choose how to start: Use preset, Ask AI, or Blank collection.
- For a preset, choose a useful starting structure such as Article, Person, Organization, Place, or Category. Give the collection a clear name.
- For AI, describe the content type, fields, sample items you need, and how it should appear on the site. Put request in chat prepares the request; send it from chat to start the work.
- Open the collection and review its fields before adding a large amount of content.
Choose field types that match the information
- Text: a short label, summary, role, or other plain text.
- Content: a formatted article body or longer rich text.
- Image, Link, and Place: an image, a destination URL, or an address.
- Number, Toggle, Date & Time, and Color: values that have a specific format.
- Options: a controlled list of choices.
- References: links to items in another collection, such as an article's author or categories.
Maintain the structure
Open the collection's Fields editor to add or adjust fields. A field label is the human-readable name. The field ID identifies it for connected pages and cannot be changed after creation. Use a clear label, and keep the ID stable once pages depend on it.
Defaults provide starting values for new items; changing a default is not a bulk rewrite of existing content. System fields such as title, slug, and publication date have protected behavior. Removing a field can affect pages that use it, so inspect connected pages afterward.
Publish a usable result
Add one realistic test item and view it on a connected page before filling the entire collection. Check that long titles, missing optional images, and references render sensibly. Collection field changes must be published to update the public structure. Publish the items themselves as well when they should become visible. Review generated sample content and replace fictional or placeholder claims before making them public.