A Webflow CMS your marketers won't break
Structure collections around how a marketing team actually works.
Most Webflow CMS collections get structured the way a developer would model a database: normalized, deduplicated, reference-heavy. It is clean. It is also the reason a marketer opens the CMS six months later and has no idea where to add a page.
The team that runs the site every day is the real user of the CMS - not the developer who built it once and left.
Structure for the editor, not the schema
Start from the jobs a marketer will actually do: launch a landing page, update a pricing tier, swap a testimonial.
Fewer, chunkier collections beat many normalized ones - every time a human, not a query, is doing the reading.
In practice this means resisting the urge to split every repeated block into its own reference collection.
Name things the way the team talks
Field and collection names should match the vocabulary the marketing team already uses in meetings.
A minimal reference pattern that scales
When you do need references - authors, categories, related case studies - keep the reference shallow. One hop, never two.
What this looks like in the class list
A short, boring class list is the tell. If your Webflow class panel reads like a sentence a marketer could write, you are structured correctly.
When should you break a CMS collection into multiple?
When two kinds of content genuinely have different fields and different places they get used — not just because one has slightly more variety.
How do you handle nested references in Webflow?
Keep references to one hop wherever possible. If you find yourself needing two hops to render a single field, flatten the second collection into the first.
Do CMS items count toward site plan limits?
Yes — every collection item counts toward your CMS item limit regardless of whether it renders a page.
Enjoyed this? We build the systems we write about.
Fixed monthly retainers on Webflow and Medusa JS — by the same people who wrote this.