FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 3 of 6

Components and CMS model

The biggest structure choice in a build: should this be a component, a CMS collection or a one-off section? Decision rules, field standards, and real project examples.

7 min readUpdated 2026-11-07
All chaptersChapter 3 of 6
  1. 01Brief and Figma handover
  2. 02Client-First, classes and variables
  3. 03Components and CMS model
  4. 04Interactions that stay fast
  5. 05Editor handover
  6. 06Pre-launch checks

The short answer

Use a component when the design repeats and the content is set by hand, a CMS collection when you have many items that need their own page, or need to be filtered or created from data, and a plain section when something truly appears once. Plan these choices on paper before you build, with three real items for each collection.

Get this wrong and the site still looks fine on launch day. The cost shows up later, when one small change needs dozens of manual edits. Our Webflow CMS guide explains collections, fields and references from the start. This chapter gives the rules for choosing between them.

Component, CMS or section?

QuestionIf yesReal example
Does it need its own URL, per item?CMS collection with a template pageClanX role pages all come from one CMS template.
Will pages be created from data, by a script or an API?CMS collectionClanX creates role pages by sending data to the CMS API.
Will people filter or search a long list of it?CMS, usuallyPetavue CMS lists use filters and load more.
Does the same item show in several places?CMS, with referencesFor example, case studies, resources and people live in collections and show wherever they belong.
Is it one design used with different words and images?Component with propsThe same revamp builds every section as a component.
Will the owner add cards without a CMS?Component with props, with code doing the restBailey adds cards and sets a category prop. The filters build themselves from those categories.
Will a page get copied and filled in for each use?Page built from componentsBailey duplicates a noindex outreach page and fills it in through props.
Does it appear once, ever?A plain sectionA one-off hero.

Decision rule Ask who adds the next one, and how often. Frequent items added by a marketer belong in the CMS. A rare card added by the owner can be a component. Both are valid. Bailey is a good reminder that the CMS is not always the right answer.

Component standards

  • Name it by what it is. Pricing card, not Section 7.
  • A prop for each thing that changes between uses. Heading, text, image, link and visibility of optional parts.
  • Write prop names for the editor. Button label, not txt_1.
  • Decide what is global on purpose. Webflow says marketers and content editors can edit unbound text, links and images inside a component, and those changes reach every instance. If a value must differ per page, bind it to a prop.
  • Nav, footer, buttons and CTA blocks are components from day one.
  • Show each one on the style guide page, with its longest likely content.

A useful test: drop the component on a blank page, fill in the props with long, awkward text, and shrink the window down to phone width. If it breaks, fix the component, not the page it is on.

Plan the CMS on paper first

Do this before you make any collection. Changing a model after items are in is slower than getting it close the first time. Here is a filled-in example, for a case study collection.

FieldTypeWhyNote for editors
NamePlain textCard title, and the default titleKeep under 60 characters
SlugDefaultThe URLDo not change after publishing without a redirect
SEO titlePlain textDiffers from the card titleUnique per item
SEO descriptionPlain textSearch and socialOne or two plain sentences
Client logoImageCard and page headerSVG if possible, with alt text
SummaryPlain textCards and listsOne sentence
BodyRich textThe storyHeadings start at H2
ServiceReferenceFilter and related listsPick one from the list
FeaturedSwitchHome page listTurn on for no more than the list shows

Write a note on every field that could confuse someone, and keep the note in the field's help text where Webflow lets you.

Field standards

ChoiceUse thisBecause
Short fixed list that rarely changesOption fieldNo extra collection to look after
A list that has its own details or its own pageReference fieldOne source for that thing, such as an author with a photo and a bio
Many of them per itemMulti-referenceTags and related services
Text that needs headings, links or listsRich textEditors can format it safely
Text that must fit a designPlain textEditors cannot add a heading that breaks a card
Sort order set by handNumberClear and easy to change

On limits, the Webflow CMS API guide says a collection schema can have up to 60 fields, along with the default name and slug. Reference field limits and item counts depend on your plan and can change, so check the current docs before you commit to a model that needs a lot of them. Nearing a limit is usually a sign that one collection is doing two jobs.

Lists, filters and load more

On Petavue, CMS lists use Finsweet Attributes for filters and load more, so the team does not have to maintain custom code. If you use them, these points come from Finsweet's own docs for List Filter and List Load.

  • Filters use fs-list-element and fs-list-field attributes, and the values on the filter and on the item must match.
  • They do not run in Design, Edit or Preview mode. Test on the published site after each change.
  • Load More needs native "Paginate Items" turned on, and items per page sets how many load per click.
  • Render All can hurt performance on large collections, especially on phones. Avoid it on big lists.
  • Interactions will not fire on newly loaded items unless you add the reset attribute, which also restores elements to their initial state. Test it.
  • Loaded pages are cached until you republish. If content changes through the API without publishing, read the cache setting.

Use the current version of Attributes, and read its docs for each feature rather than copying old snippets.

Pages from data

ClanX shows the pattern: role data goes in as CMS items, and one template turns each into a full landing page, so a design change on the template updates every role page. Our post on Webflow CMS API landing pages covers the how. These are the standards to hold to.

  • Design the template with the longest and the shortest real items first.
  • Each page must say something unique. Check that fields hold real differences. A swapped job title is not enough.
  • Create items as drafts first, and read a few as a person before they go live. The API guide covers staged and live items, and draft flags.
  • Decide who owns the data source, and what happens to a page when a role closes.
  • Rate limits and publishing rules can change, so check the current docs before you plan a large run.

Check the model before filling it

Load three real items, and then try the awkward cases.

  • An item with no image. An item with a very long title. An item with an empty optional field.
  • Empty lists show something sensible, or the block hides itself.
  • A related list shows the right items, and does not include the current page.
  • A marketer can add one item from start to finish, without help.

Done when A person who was not on the build can add an item and read back the rule for what goes where. If you would like us to plan the model, that is part of our Webflow CMS work.

Takeaways

What to remember from chapter 3.

  • CMS for items with their own URL, filters or data sources. Components for one design with different content. Plain sections for true one-offs.
  • Ask who adds the next one, and how often. That usually settles it.
  • Bind anything that changes per page to a prop. Unbound component content changes everywhere.
  • Model the CMS on paper with three real items before you create a collection.
  • Attributes only run on the published site, so test there after each change.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.