Why collections matter more than pages
A static page is designed once and edited forever. A collection is designed once and populated indefinitely. Once the template exists, adding the hundredth case study costs the same as adding the second.
This is the difference between a site your team can grow and one where every new page is a developer ticket.
| Content | Collection or static page | Why |
|---|---|---|
| Blog posts, case studies | Collection | Repeating shape, growing count |
| Team members, integrations | Collection | Repeating shape, reused across pages |
| Homepage, about | Static page | One of a kind, bespoke layout |
| Service pages | Usually static | Each argues differently |
| Locations, job openings | Collection | Repeating, and often filtered |
Designing a collection well
The field list is the decision that matters. Too few fields and editors paste formatted blobs into a rich text field; too many and nobody fills them in.
- Give every field one job, and name it the way an editor would
- Use reference fields for anything you will want to filter or group by later
- Keep SEO fields separate from display fields, so a title can differ from a meta title
- Set required fields deliberately: they are your only guard against half-finished entries
Collection limits worth knowing
Webflow sites cap the number of collections and the number of items per site, and those caps differ by plan. Plan the content model against the cap before you launch, not after the two-thousandth item fails to import.
Why it matters for B2B marketing teams
The decision a B2B marketing team should care about is who can publish without help. Content modelled as a collection can be added by a marketer in minutes. Content built as a static page needs whoever built it, indefinitely.