Worked example recreated through Oxygen’s interface and checked on a private frontend on 4 October 2026.
What it does and when to use it
Presents items as a conventional list. Use it for the specific job described below. If a simpler native element can deliver the same outcome, prefer the simpler structure and fewer competing styles.
Before you start
This is a Breakdance catalogue recipe for use with a compatible Breakdance Elements for Oxygen extension. It is not a guarantee of availability in your version. Check the installed element list and official reference before following the steps. This example was recreated in the private test copy using the interface steps below. Check the tested versions; another release may use different labels.
Worked example: A pre-build asset checklist
Scenario: A pre-build asset checklist. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- In Oxygen, choose Add Element and search for Basic List. Add it beneath a heading explaining which assets you need before building the page.
- In the Content tab, click the first row under Items. Set Text to “Provide final logo files.”
- Open each remaining row and replace the sample text with “Approve the final page copy.”, “Confirm image permissions, including credits and any usage limits for each supplied asset.” and “Provide a contact email for enquiries.” Use Add Item when you need another requirement.
- Open Design → List. Choose Disc as Marker Type and Outside as Marker Position. Keep a comfortable gap below each item; the tested default Below Item value was 15px.
- Save and inspect the frontend at 390px and on desktop. Confirm the requirements appear in the right order, markers remain visible and the long image-permissions item wraps without horizontal scrolling.
- Replace the sample requirements with the actual requirements for your project. Keep the phrasing parallel and remove unnecessary rows.
Tested versions and limits
Recreated through Oxygen 6.2.0-beta.9 with Breakdance Elements for Oxygen 1.1.0-beta.5 on 4 October 2026, WordPress 7.1.2 and PHP 8.5.11. The saved frontend was also checked on a private Oxygen 6.2-rc.1 copy. Browser testing used SQLite; production was not upgraded.
Normal insertion, editing all four rows, Disc markers, Outside positioning, saving and the published frontend were checked. The output contained one unordered list with four items. At 390px, the long permissions requirement occupied two lines and the document had no horizontal overflow. The marker padding kept the bullets inside the viewport.
This verifies the described static asset checklist. It is not a clickable to-do list and does not save completion state. Item links, custom markers, all typography settings and dynamic-data lists were outside this example. There is no provider-dependent empty state in this static recipe.
Expected result
You should have a pre-build asset checklist. 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 list items need paragraphs or subheadings, use richer content rather than squeezing them into short labels. Use an ordered list when sequence matters.
Checks before publishing
Use real text and assets rather than a perfect placeholder. Check a long label, narrow screen and empty-data state before publishing.
- 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 Basic List reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.
Check extension element visibility in Oxygen. An element may be hidden where a native equivalent exists.