Skip to content
Tutorials Center
My learning

Topics

Lesson 15 of 37 ยท CMS and Dynamic Content

CMS Concepts: Collections, Items and Fields

Learn what a CMS is and how collections, items, fields, references and templates work, with a runnable stand-in that models typed fields, validation, filtering and sorting.

Some content never changes: your About page, your contact details. Other content grows constantly: blog posts, products, team members, events, recipes, case studies. If you build every blog post by hand as its own page, you copy the same layout again and again, and a design change means editing a hundred pages. A CMS (content management system) solves this by separating content from design. You describe what a blog post is once, design its page once, and then add posts as data.

Webflow and Wix each include a CMS: Webflow's CMS with collections, and Wix's Content Manager with collections and dynamic pages. The names and screens differ, but the concepts in this lesson apply to both and to nearly every CMS in the world. You will model content with a runnable stand-in, which is a teaching aid and not the real product.

The vocabulary

Term Meaning Blog example
Collection A type of content, like a table Blog posts
Item One entry in a collection, like a row One specific post
Field One piece of information on every item, like a column Title, date, author
Template page The page design reused for each item The layout of any post
Collection list A repeating block that shows items on other pages "Latest posts" on the home page
Reference A field that points to an item in another collection The post's author
flowchart LR
  C["Collection: Blog posts"] --> I1["Item: Post A"]
  C --> I2["Item: Post B"]
  C --> I3["Item: Post C"]
  T["Template page<br/>(designed once)"] --> I1
  T --> I2
  T --> I3
  L["Collection list on Home<br/>(shows latest items)"] --> C

One collection, many items, one template, and any number of lists that display the items elsewhere.

Field types

Every field has a type that controls what it can hold and how the editor presents it. Typical types, with slight naming differences between tools:

  • Plain text (short, for titles and names).
  • Rich text (formatted body content with headings, links, images).
  • Number, price or currency.
  • Date and time.
  • Image and multiple images (galleries).
  • Video or file uploads.
  • Link (URL), email, phone.
  • Switch (true or false), such as Featured.
  • Option / dropdown (one choice from a list), such as Category.
  • Color.
  • Reference to another collection (one item), and multi-reference (many items), such as Tags.

Choosing the right type matters because it enables features: a date field can be sorted and formatted, a switch can filter featured posts, an option field produces consistent category labels, and a reference lets you reuse an author's bio everywhere without retyping it.

Why references beat copy-paste

Suppose each blog post stores the author's name as plain text. If an author changes their name or photo, you must edit every post. If instead you create an Authors collection (name, photo, bio) and give each post a reference field to an author, the author's data is stored once. Change the author item and every post updates. This is the basic idea of normalising data: store each fact in exactly one place.

Modeling in a stand-in

The stand-in below models a tiny CMS: a collection with typed fields, an item validator, and queries for filtering and sorting. It is not Wix or Webflow code, yet it mimics how a CMS enforces types and powers lists.

JS Stand-in: typed fields and validation

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

No output.

A real CMS stops you at the form when you leave a required field empty or type text into a number field. Those rules are the schema, and defining a good schema is most of the work of content modeling.

Lists, filters and sorts

On the site, you rarely show every item. You show a list with rules: the latest six, only featured posts, only the Recipes category, sorted newest first, skipping the first one. Both tools offer these through collection-list settings: filter conditions, sort order and a limit.

JS Stand-in: filter, sort and limit a collection

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

No output.

The last list is the classic "featured post plus more posts" layout: the first item gets a big card elsewhere, and the rest skip it. Notice that the CMS never changes the data when you change a list setting; the list is just a view of the collection.

Static versus dynamic pages

A static page is built by hand. A template page (Webflow's Collection page; Wix's dynamic item page) is designed once, with elements bound to fields: the heading shows the item's Title field, the image shows the Image field, the date element shows the Published field. When someone visits /blog/spring-menu, the platform finds the item whose slug is spring-menu and fills the template.

Planning a content model

  1. List your content types (blog posts, authors, products, locations).
  2. For each type, list the fields a page needs. Ask what you will show, filter or sort by.
  3. Find the relationships: one author to many posts, many tags to many posts.
  4. Pick the right field type for each field.
  5. Name fields clearly, in a consistent style.
  6. Decide who edits and keep the editor form simple.
  7. Check platform limits: number of collections, items and fields allowed on your plan.

Common mistakes

  • Putting everything in rich text instead of separate fields, which makes lists and filters impossible.
  • Copying author or category text into each item instead of using references or options.
  • Adding fields "just in case", making the edit form long and confusing.
  • Forgetting a slug strategy, resulting in messy URLs.
  • Treating the CMS as unlimited: plans have item and field limits.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is an item in a CMS?

    A collection holds many items. Each item holds values for the collection's fields.
  2. 2. Why use a reference field to an Authors collection?

    References avoid duplicated text and keep related data consistent.
  3. 3. What is a collection list?

    Lists display collection items on any page, driven by settings and not by copied content.
  4. 4. Which field type fits 'Category' with a fixed set of choices?

    An option field keeps values consistent and makes filtering reliable.

Summary

  • A CMS separates content (items and fields) from design (templates and lists).
  • Collections hold items, fields have types, and references connect collections.
  • Lists filter, sort and limit items without changing the data.
  • Template pages are designed once and bound to fields.
  • Model content on paper first, and keep each fact in one place.

Next: Webflow CMS: Collections and Templates