Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.
What it does and when to use it
Repeat a Component for taxonomy terms such as categories or tags. 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 category directory with genuine archive links
Scenario: A category directory with genuine archive links. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Create and describe categories in WordPress and assign posts to them.
- Create a reusable Component whose label and destination use term name and term permalink in the dynamic-data picker.
- Add Term Loop Builder, choose the category taxonomy and that Component. Decide whether empty terms should be included.
- Set the layout and responsive spacing through the loop’s controls. Open two term links and check that each archive contains the intended posts.
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 category directory with genuine archive links. 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 every category card shows a post title, bind term fields rather than post fields. A taxonomy term is a different object from the posts assigned to it.
Checks before publishing
A term is a category or tag, not a post. Bind term fields in the item, and check how empty categories should behave.
- 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 Term Loop Builder 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.