.svg)
A Webflow CMS project is much easier to build when the content structure is planned before the design starts. Without a clear plan, it is easy to create too many Collections, duplicate information, or build templates that become difficult to manage later. This worksheet helps you define what belongs in the CMS, how different types of content should connect, and what your Webflow team needs to consider before building.
Before thinking about Collections, make a list of the content your website actually needs.
Typical examples include:
Don't create a Collection simply because something appears multiple times on the website. First ask whether the content needs to be managed dynamically, reused, filtered, referenced, or displayed across multiple pages.
Once you know what content needs to be managed, start mapping it into Collections.For each potential Collection, define its purpose before creating it in Webflow.A good Collection usually represents a distinct type of content with its own properties and structure.
If two Collections contain almost exactly the same information, consider whether they could be handled with one better-designed structure.
Every Collection needs fields that describe its content.
For example, a Blog Collection might include:
Title
Slug
Featured Image
Excerpt
Author
Category
Publish Date
Content
Related Articles
Before building, write down the fields you actually need.
A strong CMS is not just a collection of individual items.Think about the relationships between them.A blog post might belong to a category and have an author. A case study might reference a service. A product might belong to a category and have related products.
Use Reference and Multi-reference fields when content needs to be connected.
Each Collection Template should have a clear structure.
For example:
Blog Template
Hero → Introduction → Main Content → Related Articles → CTA
Case Study Template
Client → Challenge → Solution → Results → Testimonial → Related Service
Write down the sections that should appear on every item and the sections that should only appear when certain CMS fields are populated.This makes it easier to create flexible templates instead of building separate versions for every content variation.
The CMS should work for the people who manage the website, not just for the developer who builds it.Define who is responsible for creating, reviewing, updating, and publishing content.
Also decide which fields are mandatory and create naming conventions that are easy for editors to understand.A field called Featured CTA is much easier to manage than an internal label that only the developer understands.
CMS planning should include SEO from the beginning.
For each Collection, consider whether you need fields for:
Not every field needs to be manually editable. The important thing is deciding early which information should be dynamic and which should remain consistent across the template.
Before creating the Collections in Webflow, review the worksheet as a complete system.
Ask:
Is every Collection necessary?
Are any fields duplicated?
Are important relationships missing?
Can editors understand the structure?
Will the CMS still work when the website is much larger?
Can the templates handle different content variations?
If the answer to these questions is clear, the actual Webflow build becomes much more straightforward.
Before starting the build:
☐ Content types are identified
☐ Collections have clear purposes
☐ CMS fields are defined
☐ Required and optional fields are separated
☐ Reference relationships are planned
☐ Collection Templates are mapped
☐ Conditional content requirements are identified
☐ Editorial workflow is defined
☐ SEO fields are considered
☐ Scalability has been reviewed
☐ Naming conventions are established
☐ Future content requirements have been considered
Good Webflow CMS planning is less about creating as many dynamic fields as possible and more about creating the right structure.
A well-planned CMS gives editors flexibility while keeping the website consistent, scalable, and easier to maintain.
.jpg)
.jpg)
.jpg)
.jpg)
