Section–Collection Matrix
Most sections store content directly -- you edit it in the visual editor. Some sections can also pull data from your collections (posts, team members, testimonials, etc.). This page shows which sections support which collections.
Compatibility matrix
| Section | Data Source | Compatible Collections |
|---|---|---|
| Hero Split | Inline | -- |
| Hero Centered | Inline | -- |
| Hero Minimal | Inline | -- |
| Features Grid | Inline or Collection | features, capabilities, benefits |
| Feature Showcase | Inline or Collection | features, services, offerings |
| Blog Grid | Collection | posts, articles, news, blog |
| Team | Inline or Collection | team, staff, members, people, employees, board, volunteers, instructors, providers, agents |
| Testimonials | Inline or Collection | testimonials, reviews, quotes |
| Pricing | Inline or Collection | pricing-plans, plans, tiers |
| FAQ | Inline or Collection | faqs, questions |
| Stats | Inline | -- |
| Logo Cloud | Inline or Collection | partners, clients, logos |
| CTA Banner | Inline | -- |
| Contact | Form | -- |
| Navbar | Global | -- |
| Footer | Global | -- |
Legend:
- Inline -- Content is edited directly in the visual editor. The section stores its own data.
- Collection -- The section can be populated automatically from a matching collection.
- Form -- The section renders a contact form rather than displaying content items.
- Global -- Navigation sections configured through the Layout Editor, shared across all pages.
How it works
Inline mode (default)
Every section starts in inline mode. You edit content directly in the visual editor -- adding feature cards, testimonial quotes, team members, and so on. Each section stores its own items.
Collection mode
When you use a site template, the template system automatically maps your collections to compatible sections. For example:
- The Blog template maps the
postscollection to the Blog Grid section - The About template maps the
teamcollection to the Team section - The Landing Page template maps
testimonialsto the Testimonials section
When a section is connected to a collection, published items appear automatically. You do not need to re-enter the data.
Custom frontends (Headless API)
If you are building a custom frontend with the Headless API, the pages endpoint automatically injects published collection items into matching sections:
GET /api/v1/public/pages/{slug}
The response includes each section's data. For sections mapped to a collection, the API merges published collection items into the section's item array. Your frontend receives the final, merged data.
Field mappings
When collection data flows into a section, fields are mapped automatically. Below is the mapping for each section that supports collections.
Blog Grid to Posts
| Section Field | Collection Field |
|---|---|
title | title |
excerpt | excerpt |
date | publishedAt |
category | categories |
image | featuredImage |
readTime | calculated from content length |
Team to Team (and similar people collections)
Works with: team, staff, members, people, employees, board, volunteers, instructors, providers, agents
| Section Field | Collection Field |
|---|---|
name | name |
role | role |
bio | bio |
image | photo |
Testimonials to Testimonials
Works with: testimonials, reviews, quotes
| Section Field | Collection Field |
|---|---|
name | author |
role | authorTitle |
company | authorCompany |
quote | quote |
avatar | authorPhoto |
rating | rating |
FAQ to FAQs
Works with: faqs, questions
| Section Field | Collection Field |
|---|---|
question | question |
answer | answer |
Features Grid to Features
Works with: features, capabilities, benefits
| Section Field | Collection Field |
|---|---|
title | name |
description | description |
icon | icon |
Feature Showcase to Features
Works with: features, services, offerings
| Section Field | Collection Field |
|---|---|
title | name |
description | description |
image | image |
ctaLabel | ctaText |
ctaHref | ctaLink |
Pricing to Pricing Plans
Works with: pricing-plans, plans, tiers
| Section Field | Collection Field |
|---|---|
name | name |
price | priceMonthly |
features | features |
cta | ctaText |
highlighted | isPopular |
Logo Cloud to Partners
Works with: partners, clients, logos
| Section Field | Collection Field |
|---|---|
name | name |
The partner's logo is rendered from the partner collection's logo field.
Tips
You do not need collections to use any section. Collections are useful when you have items that change often, like blog posts or team members.
- Start simple. Edit section content in the visual editor. Add collections later if needed.
- Collections save repetition. When the same data appears on multiple pages, store it in a collection and update it once.
- Headless API merges automatically. The pages endpoint delivers merged data -- no need to fetch collections separately.
- Static sections stay static. Heroes, CTA Banner, Stats, Contact, Navbar, and Footer always use inline or global data.
Related pages
- Sections Overview -- Browse all 16 sections
- Content Types -- Learn about collections and how to manage them
- Headless API -- API reference for fetching pages and content