Manage blogs, portfolios, and lists with CMS
Use a CMS collection when many items share the same fields and page design. Define the structure once, then add content without rebuilding every page.
Static pages work well for unique content such as Home, About, or Contact. Blogs, case studies, products, and testimonials repeat the same structure. Webflow CMS manages that repetition.
One collection, many items
A collection defines fields shared by every item. A blog collection might contain title, cover image, date, summary, and body fields. Each new post fills the same schema.
Source: webflow.com/feature/cms, accessed July 2026.
Design the dynamic template once
Webflow creates a collection template page. You design it with the same sections, divs, and classes as a static page, then connect elements to collection fields.
The heading can display the current item's title and the image can display its cover. Every item receives the same design automatically.
Display many items with a Collection List
A Collection List repeats one card design for every matching CMS item. Use it for article grids, portfolios, products, testimonials, or team members.
Use CMS only when the structure repeats
CMS is useful for growing, frequently updated sets. It can be unnecessary for two static blocks that will rarely change. Conversely, building dozens of repeatable items as manual pages creates avoidable maintenance.
Lesson checklist
- I understand a collection as a reusable content schema
- I can distinguish dynamic fields from static content
- I know when to use a Collection List
- I decided which parts of my site belong in CMS
Next, you will publish and connect the permanent domain.