Practice recipe based on public documentation; the Breakdance extension is not installed here.
What it does and when to use it
Creates a prominent linked 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 clear call to action below a project summary
Scenario: A clear call to action below a project summary. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Choose one next step, such as View the project or Open the tool.
- Use a concise label and the correct destination; style it distinctly from secondary links.
- Check keyboard focus, contrast and the touch target on a phone.
Call-to-action illustration · HTML/CSS, not an extension demo
A useful next step should describe its destination.
HTML model: navigation versus an action
<a href="/tools/">Explore the tools</a>
<button type="button">Copy result</button>A link navigates; a button performs an action. This structural example is not a claim about the uninstalled extension’s emitted markup. Replace destinations and connect any action to real behavior.
Expected result
You should have a clear call to action below a project summary. 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 clicking triggers a page action rather than navigation, ensure the implementation uses appropriate button behavior. Do not place a linked button inside another linked card.
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 Button 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.