Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.
What it does and when to use it
Display the rows of a supported ACF repeater field. This example focuses on one achievable outcome rather than listing every possible setting.
Before you start
Start with a test page and the data or assets described in the example. The values below are starting points, not universal design defaults.
Worked example: A project specification list from ACF
Scenario: A project specification list from ACF. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Create an ACF repeater field with label and value subfields in an ACF edition that supports repeaters. Assign it to the intended post type.
- Enter three specification rows on a test project and choose that project as the builder preview context.
- Add the repeater loop, select the repeater source and bind a repeated Component to the row subfields using the dynamic-data picker.
- Use the layout controls for row spacing. Preview the populated project and a project with no rows; do not use a post query to loop repeater rows.
Use the Oxygen interface
Select the element or its parent Container, choose the intended shared class, and configure layout, spacing and typography in the builder. Switch to a narrower breakpoint to make responsive overrides. You do not need to paste CSS for this example.
Expected result
You should have a project specification list from ACF. Verify the result on the frontend using the same content or object described in the steps. A correct builder preview alone does not establish that links, data or interactions work for visitors.
Troubleshooting
If rows are empty, check the selected field, post preview context and subfield bindings. Use a post loop for separate posts; a repeater loops rows stored on one object.
Checks before publishing
This needs the appropriate custom-field integration and data. A post loop and a field repeater solve different problems.
- Compare desktop and narrow-screen layouts using actual content.
- Follow every destination and operate interactive controls with a keyboard where applicable.
- Check an empty or unavailable-data state when the element depends on a provider.
Official reference and version notes
Official Repeater Field reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.
The native references were checked against the site’s Oxygen 6.2.0-beta.9 installation and public documentation. Individual recipes should still be validated in your project.