Collections
Typed content items rendered through one template page, such as a blog, glossary, or product list.
A collection is a list of items that share the same fields, like blog posts, glossary terms, case studies, or plans. You design one template page, and every item gets its own page at /{prefix}/{item}. A Collection list block shows items on any page.
Open the site's Collections tab.
Create a collection
Create Collection asks for:
- Name, such as "Glossary".
- URL Prefix, such as
glossary. Items live at/glossary/{item-slug}. The prefix can't be a built-in route, another collection's prefix, or a path that has redirects under it (/glossary/…). - Fields (see below).
Creating a collection also creates its Template Page from a starter, with the name heading and the first fields already bound.
A new collection serves nothing until you Publish the site. Collections and their templates are part of the published snapshot.
Index page
A page may use the same slug as a collection. That page is the collection's index: for example, a page glossary at /glossary with a Collection list of every term, while the terms live at /glossary/{slug}.
Fields
Every item has a built-in Name and Slug, plus SEO & Social settings (title, description, social image, noindex). Add up to 30 more fields on the Fields tab:
| Type | Stores |
|---|---|
| Text | A single line or short paragraph, up to 2,000 characters |
| Rich Text | Formatted text with headings, lists and links, up to 20,000 characters. Unsafe HTML is removed |
| Image | An image from Storage (/media/{assetId}) |
| Number | Prices, ratings, counts |
| Yes / No | An on/off switch |
| Date | A date like 2026-01-31, or a date and time |
| Link | A path like /pricing or a full https:// URL |
| Option | One choice from up to 50 options you define |
| Reference | One item in another collection |
| Multi-Reference | Up to 20 items in another collection |
| List | Repeating rows, up to 50, each with the same 1–8 sub-fields (Text or Rich Text) |
Each field has a key (used in bindings, CSV columns, and the API), a label, optional help text, and Required. Keys start with a lowercase letter and use letters, digits, and _. name, slug, seo, id, and url are reserved.
Removing a field stops rendering it but keeps the stored values, so adding the same key back restores them.
List fields
A List field holds repeating rows, such as FAQ entries, feature bullets, or steps. Define 1–8 sub-fields (itemFields in the API), each with its own key, label, and type (Text or Rich Text). An item can have up to 50 rows. Use FAQ Preset creates a list with question (Text) and answer (Rich Text) sub-fields.
In CSV import and export, a list field is one cell holding a JSON array of rows, for example [{"question":"Is there a trial?","answer":"<p>Yes, 14 days.</p>"}].
Template page
The template is the layout for every item. Open it from the collection's Template Page link. It does not count toward your page limit and has no address of its own. Template changes go live on the next site Publish.
Use Preview With Item… in the editor to fill the canvas with a real item while you design.
Bind blocks to fields
Select a block, then use Bind to Field… next to a property. A bound property shows a field chip with an unbind control. These properties can be bound:
| Block | Bindable properties |
|---|---|
| Text, Heading | Text, rich text |
| Button, Link | Label, link |
| Image | Image, Dark Mode Image, alt |
| Video, Embed | Source, poster |
A binding is a field path:
| Path | Value |
|---|---|
name | The item's name |
{fieldKey} | A field on the item, such as summary |
{refField} | The names of the items a reference field points to |
{refField}.name | The referenced item's name. Also .slug, .url, .id, .{fieldKey} |
item.url | This item's own path, /{prefix}/{slug} |
item.slug | Also item.name, item.id, item.publishedAt |
Bind an FAQ to a list field
On the template, select an FAQ block and click Bind Questions to Field to fill it from a list field. Each row becomes one question. By default the block reads the question and answer sub-fields; pick other sub-fields if your list uses different keys. Each item page then also gets FAQPage structured data built from its own rows.
Values are made safe when the page is built: text, alt, and labels get plain text; rich text is cleaned; links must be safe URLs; images must come from Storage. A missing or unsafe value renders empty, so the editor placeholder never reaches visitors.
SEO for item pages
Each item page uses the item's SEO title and description. Without them, the title falls back to the item name and the description to the first text field.
Collection list block
Add Collection list to any page, including the template, to repeat a card for each item. It holds one card container: design one card with bound blocks, and it repeats per item.
| Setting | Options |
|---|---|
| Source | A collection, or (on a template) a Multi-Reference field of the current item |
| Sort | Any field, or order, name, or published date; ascending or descending |
| Filter | One field with equals, does not equal, contains, or is set |
| Limit | 1–100 items (default 12) |
| Empty text | Shown when nothing matches (default "Nothing here yet.") |
Only published items appear. Sorting, filtering, and the limit run on the server.
References
A Reference or Multi-Reference field points at items in another collection (or the same one). On the item page, a reference gives you that item's name, slug, URL, and fields, one level deep. In the API and CSV, reference values take item ids or item slugs from the target collection.
Deleting an item removes it from every other item's reference fields. The confirmation dialog shows how many items point at it.
A collection that another collection's reference field points at can't be deleted. Remove that reference field first.
Publishing
| Status | On the live site |
|---|---|
| Draft | Not shown |
| Published | Shown, at the last published version |
| Archived | Not shown. Kept, and still counts toward your item limit |
Editing a published item does not change the live page until you publish it again. The items table marks it as changed.
There are two ways to publish items:
- Save & Publish in the item editor, or Publish in the items table's bulk actions, puts items live right away through the template that is currently published. This needs the site to have been published once.
- Publish on the site also publishes every Published item with unpublished changes, in the same step as your pages.
Unpublish takes items off the live site and keeps them as drafts. Archive also takes them off the live site and hides them.
Publishing, unpublishing, and archiving or deleting live items need permission to publish the site.
Roll back in Versions restores pages, the header and footer, and templates. It does not restore item content: items stay at their latest published version.
Import and export CSV
Import CSV walks you through four steps:
- Upload a CSV file with a header row.
- Map Columns to fields. Columns whose header matches a field key or label are mapped for you. Map one column to Slug.
- Review the first rows and any row problems.
- Import. Rows update the item with the same slug, or create a new draft. Existing items keep fields a row leaves out and keep their status. Up to 200 rows import right away; larger files import in the background.
Nothing is published by an import.
The import dialog also has Export the current items, which downloads every item as CSV with one column per field. Cells that a spreadsheet would run as a formula (starting with =, +, -, @, tab, or carriage return) get a leading '. Importing the file again strips it, so an export round-trips.
Structured data
On the collection's Settings tab, pick a schema.org type and map its properties to fields. The item's name, URL, and description are filled in for you.
| Type | Properties you can map |
|---|---|
| Glossary Term (DefinedTerm) | Term, Definition, Term code |
| Article | Headline, Description, Image, Date published, Author |
| Product | Name, Description, Image, Brand, SKU |
| App or Tool (SoftwareApplication) | Name, Description, Category, Operating system, Image |
The node is added to each item page's JSON-LD graph. DefinedTerm items also get inDefinedTermSet set to {your domain}/{prefix}, the index page.
An FAQ block bound to a list field adds FAQPage to each item page.
When the index page (the page whose slug matches the prefix) has a Collection list of a DefinedTerm collection, it gets a DefinedTermSet node listing the terms. See Crawlers and agents.
Sitemap
Published items are listed in the sitemap with their last publish date.
Limits
| Limit | Value |
|---|---|
| Items per site | Business 1,000; Agency unlimited |
| Fields per collection | 30 |
| Items per Collection list | 100 |
| References per Multi-Reference | 20 |
| Rows per import | 20,000 |
Pages per site on Business is 50. The template does not count.
With MCP or the API
- MCP:
planeward-site-collection-*for collections andplaneward-site-collection-item-*for items. See MCP → Sites. - REST:
/sites/{siteId}/collectionsand its items. See REST API → Sites.
Planeward Docs