What are CMS collections?

How it works

You define a collection once by choosing its fields: for a case study, maybe client name, industry, summary, cover image, results and body text. Each case study is then an item that fills in those fields. One template page lays out the fields, and every item gets its own page at its own URL, such as /work/client-name.

Webflow and Framer both call these CMS collections. Coded frameworks have the same idea; Astro, for example, calls them content collections. Collections can also be linked, so a case study can reference an industry and a service.

Why it matters for B2B websites

Most of a B2B site’s growth happens in collections: new case studies, posts, integrations, job openings, glossary terms. Well-planned collections let a marketing team publish a polished page by filling in a form, without design work and without breaking the layout.

Poorly planned collections cause the opposite: rich-text fields used for everything, so every page looks different, or missing fields that force someone to hard-code content.

Planning tips

• List the content types you will publish in the next year before building
• Give each piece of information its own field, so it can be filtered and reused
• Add SEO fields: title, meta description and share image
• Use reference fields to connect items, such as case study to industry
• Check your platform plan’s item limits against your expected volume

Example

This glossary works like a collection: each term is one item with the same fields (name, one-sentence definition, explanation, questions, related terms), and a single template turns each into a page.

How we handle it

We plan collections with your team around what you publish and who publishes it, then build templates that look right with short and long content. Every Webflow and Framer handover includes a recorded walkthrough of adding items.

Last updated 15 November 2026