Introduction
The Framer CMS stores repeating content as collections, where each collection is a set of items sharing the same fields. One layout renders every item, so ten blog posts or three hundred products are the same amount of design work as one.
The part worth thinking about is not how to use it; that is straightforward. It is what you decide to model, because that is the expensive thing to change.
Collections Versus Pages
Anything that repeats with the same shape belongs in a collection. Blog posts, projects, team members, products, treatments, case studies. Anything that exists once and looks unlike everything else, such as an about page, is just a page.
The test is whether you would want to list, filter or sort them. If yes, it is a collection, even if there are currently only two of them.
Detail Pages Do the Repetition
A detail page is one layout bound to a collection. You design it once against a single item, and Framer generates a page for every item at its own URL. Change the layout and every item changes with it, which is the entire point.
Model it as | Because |
|---|---|
A collection with real fields | You can list, filter and sort it later |
Separate fields, not one rich text blob | Fields can be reused and displayed apart |
A boolean or option for state | Filters read it, humans do not have to |
A page, when it exists once | A collection of one is just overhead |
Fields Are the Decision That Lasts
Putting everything into one rich text field feels fast and costs you later, because nothing inside it can be listed, filtered or shown anywhere else. A date that is part of a paragraph cannot sort. A price inside prose cannot be compared.
If you might ever want to show a value on its own, it needs to be its own field. That single rule prevents most CMS rebuilds.
Filtering Comes From Structure
Collection lists filter on field values, so a filter you want later has to exist as a field now. Adding the field afterwards is easy; backfilling it across two hundred existing items is the part nobody enjoys.
Before You Build
Write down every list you might want on the site, then check that each one is answerable from the fields you have planned. If you want to see this modeled properly before building your own, the collections are visible in every demo across our Framer templates, and breakpoints are the other concept worth understanding early. The lists you forgot are exactly the fields you will wish you had added.
