Practice recipe based on public documentation; the Breakdance extension is not installed here.
Choose the right reference
Breakdance Elements for Oxygen adds catalogue elements inside Oxygen 6 and later. It is distinct from the separate Breakdance Builder product and from Oxygen Classic. This library separates native Oxygen guides from Breakdance catalogue recipes so you can choose the relevant workflow.
Before installing or following a recipe
- Confirm the Oxygen version installed on your project.
- Obtain the compatible extension from your Oxygen account and follow the official installation instructions.
- Check the elements actually available in your Add panel.
- Use a staging page with real sample content before changing an important layout.
The extension is not installed on benjaminolsen.dev. Its 145 catalogue recipes are documentation-based practice examples, not recordings of executed extension builds or a promise that every catalogue item exists in every release.
Learning path: a project listing
- Learn the native Container to group project copy and images.
- Use a Container Link when a whole card has one destination.
- Learn Components to reuse the card design.
- Use Post Loop Builder when projects or guides are separate WordPress posts.
This path covers the core task with native elements. Add an extension element only when it supplies a specific capability you need.
Learning path: interactive explanations
For expandable troubleshooting, start with the Advanced Accordion recipe and its content child. For alternate views, read the tabs and content-toggle recipes. Each recipe identifies its expected parent relationship and checks keyboard/touch behavior. A native HTML illustration in an article is labelled as such; it is not presented as a tested extension demo.
Understand optional dependencies
- Form Builder: Oxygen’s dedicated Breakdance Forms extension is also required for this workflow.
- WooCommerce: product, cart, checkout and customer-account elements require the store integration and real data context.
- Facets: FacetWP and WP Grid Builder elements depend on their named plugins and a supported results listing.
- Social embeds: public source access, platform behavior and consent settings can affect visitors’ results.
Troubleshooting: missing elements and styling conflicts
If an expected element is absent, inspect Oxygen’s element visibility settings and the installed extension version. Some catalogue equivalents are hidden when a native Oxygen element covers the same role. Use a native Container or Text where it solves the task.
For extension styling, begin with its element-specific controls. Inspect the actual frontend markup before writing an override. Do not assume a class targets an inner control, or set the same property through two competing mechanisms.
How this documentation is maintained
These are independent, AI-assisted guides for practical learning. Each element reference includes a purpose, a worked scenario, expected result, diagnostic advice and links to related topics. Scenarios are practice recipes, not invented client case studies. The native installation is Oxygen 6.2.0-beta.9; extension availability remains version-dependent.
Official references: extension overview, element visibility, extension styling and forms overview.