Webflow CMS setup

Model the content first

List every type of repeatable content the site publishes or will publish. For each, write down what an item contains, how it is shown on its own page and in lists, how it is filtered or sorted, and how it relates to other types. For example, a case study might belong to a service and feature a team member. This model becomes the blueprint for collections, and getting it right on paper is far cheaper than restructuring populated collections later.

Choosing field types

Linking collections

References let one item point to another, such as an article to its author or a project to its services. They avoid typing the same information in several places and let lists be filtered by relationship. Use them where a relationship is real and reused; too many cross-links make the CMS harder for editors to understand and can complicate templates.

Collection templates and lists

Each collection usually has a template page that displays a single item, plus lists elsewhere on the site that show several items. Design both with real content of varying lengths, including long titles and missing images, so layouts hold up when editors add content you did not anticipate.

Setting up a Webflow CMS

1. 01

   Content model

   Types, fields, relationships on paper.

   Output: Approved model

2. 02

   Plan check

   Limits against expected content.

   Output: Plan decision

3. 03

   Collections

   Built with fields and help text.

   Output: Empty collections

4. 04

   Templates and lists

   Designed with real content.

   Output: Working templates

5. 05

   Editor handover

   Guide and walk-through.

   Output: Confident editors

Example: a CMS for a property consultancy

Before building collections

The editor's view

Editors see a form for each item. Name fields clearly, order them logically, mark required ones and add short help text, such as recommended image sizes or summary lengths. Test the form with someone who will actually use it, and adjust before content entry begins.

Plan limits

Webflow plans set limits on CMS content, and these differ by plan and change over time. Estimate how many items each collection will hold in a year or two and check against Webflow's current pricing page, so you do not reach a limit unexpectedly or pay for more than you need.

Search fields

Add fields for page title and description where they should differ from the headline, and make sure image fields have alt text. Collection URLs are often generated from a slug field; settle the slug pattern early, since changing it later means redirects.

Importing existing content

If content already exists in spreadsheets or another system, prepare it to match the collection fields before importing. Check Webflow's current import options and test with a few items first, then review formatting and images.

When not to use a collection

Not everything belongs in the CMS. Content that appears once, such as an about page, or a short list that rarely changes, may be simpler as a static section. Collections earn their place when content repeats, grows or needs listing in several places.