Practice recipe based on public documentation; the Breakdance extension is not installed here.
What it does and when to use it
Makes a group of child content one link. 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 project card with one clear navigation target
Scenario: A project card with one clear navigation target. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Choose one project destination for the entire card.
- Keep the title and image inside the wrapper without nested links or buttons.
- Check focus visibility on the complete clickable region.
One linked card, one destination
<a class="project-card" href="/projects/example/">
<h3>Example project</h3>
<p>Read how the project was built.</p>
</a>Keep child anchors and buttons out of this wrapper. The example destination must be replaced; this is an HTML relationship rather than an extension control specification.
Expected result
You should have a project card with one clear navigation target. 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 the card also needs a download action, place that action outside the linked wrapper. Nested anchors produce invalid and confusing interaction.
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 Wrapper Link 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.