Framer | CMS Lists Simplify Repeating Website Content
Framer added the CMS List field on September 8, 2026, offering a cleaner structure for repeating website content. Instead of expanding a collection with numbered pairs of fields, editors can manage related rows together and connect them to a repeated visual component.
A list can describe the content more naturally
The List field groups repeating items and supports adding or reordering rows. The update also includes API and Agent support, with a Repeat property for displaying a designed card for each list item.
An FAQ page illustrates the benefit. A fixed set of Question 1, Answer 1, Question 2, and Answer 2 fields makes the content model depend on a predetermined count. A list better reflects the editorial task: add a question, revise an answer, or move an item to a more useful position.
Migration needs a visual check after the data changes
The Framer Agent can convert repeated CMS fields into a List and reconnect the data on the canvas. A list not yet displayed can be added from the Insert panel.
After migration, compare the visible order and content with the original page. Check a short list, a long list, and an empty case. The structure may be simpler, but the component still needs to explain what happens when an editor adds or removes an item.
Design one good item before repeating it
Give the repeated card a clear internal hierarchy. A title, short explanation, and optional action should remain understandable with varied lengths. Avoid relying on every row having exactly the same amount of text.
For a tutorial, the order may carry meaning; for a feature list, grouping may matter more. Choose the arrangement around the reader's task. Repetition creates visual consistency, while the editorial sequence determines whether the information is easy to follow.
A flexible model still needs editorial boundaries
Explain what belongs in each row and which details are optional. A content editor should be able to add a useful item without guessing whether a field expects a title, a paragraph, or a destination.
When building a reusable template, include an example with realistic content. Test unusually long text and repeated cards at narrow widths. This gives the buyer or future editor a better starting point than a perfectly balanced demo that hides the layout's limits.
REMEMBER: After converting repeated fields, verify item order, canvas bindings, empty lists, and responsive behavior with realistic content.{alertSuccess}
Daisuki's Take: What This Means for Web Designers
We see the List field as a content-model improvement as much as a visual feature. It lets the collection describe a group of related items without making the editor manage an increasingly long row of numbered fields.
For template creators, we would pair the new structure with a robust card and clear editing guidance. The component should tolerate the variations that come with real publishing.
The useful outcome is less friction when content grows. A list that remains easy to reorder and a layout that remains readable can make an ordinary maintenance task much more predictable.
Sources and Recommended Links
- CMS List Field | Framer Updates Official Site
