Repeater collections render a template once per row — ideal for lists, cards, and galleries that export to ACF repeaters.
Where: CMS → collection kind "repeater" — Create a repeater and bind a template
Key ideas
- Row schema: A repeater collection defines the typed fields available on every row.
- Repeated design template: One bound card/list-item structure is rendered once for each row and exports as the corresponding ACF repeater.
- Remote merge policy: Selective WordPress publishing can keep extra rows, replace the list, fill only an empty list, or skip repeater writes.
Steps
- Create a repeater collection and define stable typed row fields.
- Design one representative card/item and bind each child to a row field.
- Preview with zero, one, many, long, and missing-value rows.
- Before WordPress publish, choose the repeater policy that matches whether remote-only rows must be preserved.
Design and data concerns
- Keep the repeated item as one coherent container.
- Configure list/grid wrapping and gaps on the repeater root.
- Provide an empty state and test oversized content.
- Avoid Replace when WordPress contains rows the canvas does not own.