Menu
Content (CMS)
When to use a collection
Explains when content belongs in a collection and when it belongs on a page.
A collection is a set of items that all have the same fields. Blog posts, products, team members, events and job openings are typical collections. Each item is one post, one product or one person.
Text that belongs to one page, such as your homepage headline or the paragraph on your About page, stays on the page. You edit it on the canvas.
Use a collection when
- You have many entries of the same kind, and you expect to add more.
- Each entry has the same pieces of information (for example, a title, a date, an image and a body).
- You want a page that lists the entries, and often a page for each entry with its own address, like
/blog/my-first-post. - Someone should be able to add or update entries without touching the page design.
Keep it on the page when
- The text appears once, in one place.
- It's part of the design, like a section heading or a button label.
- There are only a handful of entries that rarely change, such as three feature cards on the homepage.
| Content | Where it goes |
|---|---|
| Blog posts, news, case studies | Collection |
| Products, services, menu items | Collection |
| Team members, testimonials, FAQs you add to often | Collection |
| Homepage hero text | Page |
| Contact details in the footer | Page |
| A one-off "About us" story | Page |
What a collection gives you
- A form for each item. The CMS view shows each item as a form with the right control for each field: a date picker for dates, an image picker for images, and so on.
- Publishing that's separate from your site. You publish an item on its own. It goes live within a few seconds, without republishing the whole site. See Publish and unpublish items.
- One design for every item. The listing page and the item page are built once. Every item uses them.
- Help from the AI. The AI can create collections, add fields and write items for you. Items the AI writes are drafts until you publish them.