Skip to content
Tutorials Center
My learning

Topics

Lesson 16 of 37 ยท CMS and Dynamic Content

Webflow CMS: Collections and Templates

Step through Webflow's CMS workflow: creating a collection and fields, designing the collection page, binding elements to fields, building collection lists with filters, and using references and conditional visibility.

Webflow's CMS is one of the reasons designers choose it: you design real, custom layouts and still let editors add content through a simple form. The workflow has five steps: create a collection with fields, add items, design the collection page (the template), show items elsewhere with collection lists, and publish. This lesson walks through each step in words, so that you can repeat it in your own Webflow account.

The Webflow product cannot run on this site. Menu names and layouts may change between versions, so read the instructions as a map. A stand-in simulates template binding so you can see what the Designer does when you connect an element to a field. It is a teaching model, not Webflow code.

Step 1: create a collection

  1. Open the CMS panel in the Designer's left sidebar and choose to create a new collection.
  2. Name it in the plural (Blog Posts). Webflow derives the singular (Blog Post) and the URL folder (/blog-posts/), which you can change.
  3. Webflow adds default fields such as Name and Slug. The slug becomes the last part of each item's URL.
  4. Add your own fields: choose a field type, name it, mark it required if needed, and add help text for editors. Typical blog fields are a summary (plain text), a main image, a body (rich text), a published date, a category (option) and an author (reference).
  5. Save the collection. Webflow also generates a collection page (the template) automatically.

Plan the slug

The slug is generated from the Name by default (for example Spring menu becomes spring-menu). Edit it when titles are long or may change, and avoid changing it after publication, because the old URL would stop working without a redirect.

Step 2: add items

Items are added in the CMS panel or in the Editor (the simplified editing interface for non-designers), or imported from a spreadsheet (covered in CMS Data Modeling and Import). Each item shows a form with one input per field. Items can be draft (not published), published or archived, which gives editors a safe way to prepare content.

Step 3: design the collection page

The collection page is a normal page with a special ability: elements can be bound to the fields of the current item. To bind:

  1. Add an element, such as a Heading.
  2. In the element's Settings panel, choose to get text from a field and pick one (for example Name).
  3. For an image, choose get image from a field. For a link, get link from a field. For rich text, add a Rich Text element, which shows the formatted body field and lets you style the headings, paragraphs, lists and images inside it with the element's own class.
  4. Preview with different items to see how the design handles long titles, missing images and short bodies. A template must work for the shortest and the longest content.

Purple highlights usually mark elements connected to CMS data in the Designer, which helps you see what is dynamic.

JS Stand-in: binding a template to item fields

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that plain-text fields are escaped (the <menu> in the name does not become a tag), while the rich text body is trusted HTML produced by the editor. Real platforms do this for you.

Step 4: show items with collection lists

To display items on the home page, a category page or inside another template:

  1. Add a Collection List element and pick the collection.
  2. The list contains a Collection List Wrapper, the Collection List, and a Collection Item. Design one collection item (a card), and Webflow repeats it for each item.
  3. Bind each card's elements to fields, and add a link to make the whole card clickable: set the link to the current item's page.
  4. Open the list's settings to define:
    • Filter: show only items matching conditions (category equals Recipes, featured is on).
    • Sort: by a field, ascending or descending, such as Published newest first.
    • Limit: maximum number of items (for example 6).
    • Offset: skip the first n items.
    • Pagination and items per page, for long lists.

Collection lists have an item limit per list, so for large collections you paginate. Check the current limits in Webflow's documentation.

flowchart LR
  A["CMS items"] --> B["Filter"]
  B --> C["Sort"]
  C --> D["Offset and limit"]
  D --> E["Repeat the card design<br/>for each item"]

A collection list passes items through the same four stages, in this order.

Step 5: references and conditional visibility

A reference field links one item to another, such as a post to its author. On the post template you can bind the author's name and photo through the reference. A multi-reference field links to many items (tags). To show all posts by an author, add a collection list on the author template and filter Posts where Author equals the current author.

Conditional visibility hides an element when a condition fails, such as the author photo when no photo exists, or a Featured badge when the switch is off. Without it you would see empty boxes and broken layouts.

JS Stand-in: conditional visibility and references

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Editors and the Editor mode

Webflow's Editor lets content people change text, images and CMS items directly on the live-looking page, without access to design controls. Give content roles to people who only need that. They can create and edit items, but the structure (collections, fields, template design) stays protected.

Webflow CMS checklist

  1. Plan fields and references on paper.
  2. Create collections with clear plural names and field help text.
  3. Mark essential fields required, so that templates never break.
  4. Design the collection page, then preview with extreme content.
  5. Build lists with sensible filters, sort order and limits.
  6. Use conditional visibility for optional fields.
  7. Set the SEO title and description patterns for template pages (lesson in chapter 7).
  8. Publish, and after later changes test a few item URLs.

Common mistakes

  • Designing the template with perfect content only. Test long titles, missing images and tiny bodies.
  • Forgetting to link cards to the item page.
  • Using a plain-text field where a reference is needed, duplicating data.
  • Publishing with draft items still visible in lists (check item status).
  • Changing slugs after launch without redirects.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the Slug field of a CMS item determine?

    The slug is the URL segment for the item's page, such as /blog-posts/spring-menu.
  2. 2. What is the correct order of stages in a collection list?

    Items are filtered, sorted, then offset and limited, and the card design repeats for what remains.
  3. 3. Why use conditional visibility?

    Optional content such as a photo or badge should disappear when it does not exist.
  4. 4. What should you test when designing a collection page?

    Templates must cope with the extremes of real content, not just ideal samples.

Summary

  • Create a collection with typed fields, then design its collection page and bind elements to fields.
  • Show items elsewhere with Collection Lists, using filter, sort, offset, limit and pagination.
  • References connect items across collections, and conditional visibility hides optional content.
  • Content editors can work in the Webflow Editor without touching design.
  • Test templates with extreme content and avoid changing published slugs.

Next: Wix CMS and Dynamic Pages