Practice recipe based on public documentation; the Breakdance extension is not installed here.
What it does and when to use it
Presents a plan’s price, features and action. 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.
Worked example: A comparison of genuine service packages
Scenario: A comparison of genuine service packages. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Define each package's real price, scope and limitations first.
- Use consistent rows so visitors can compare the same features.
- Link each action to the appropriate next step and explain any billing period or conditions.
Expected result
You should have a comparison of genuine service packages. 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 prices or inclusions change, update all comparison rows together. Avoid fake crossed-out prices and ambiguous labels such as Everything included.
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 Pricing Table 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.