Practice recipe based on public documentation; the Breakdance extension is not installed here.
What it does and when to use it
Provides a structure for composing a product layout. 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. Exact control labels can differ; this recipe has not been executed on this site. WooCommerce and appropriate product, cart or checkout data are required. Use staging and a sandbox gateway for purchase-flow tests.
Worked example: A custom product layout using real store fields
Scenario: A custom product layout using real store fields. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Plan the title, gallery, price, options and description around the purchase decision.
- Compose supported product parts in a valid single-product context.
- Preview simple and variable products and verify that their required options remain usable.
Expected result
You should have a custom product layout using real store fields. 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 options or cart actions break, restore the supported product structure before styling further. A custom layout must preserve product-specific behavior.
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 ProductBuilder 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.