All topics

Guide

Breakdance Button: A clear call to action below a project summary

A clear call to action below a project summary. Learn when to use Button, follow a practical setup, and diagnose common problems.

3 min read · Updated 4 October 2026

Worked example practically tested in a private Oxygen installation on 4 October 2026. See the tested versions and limits below.

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. The worked example below was recreated through Oxygen’s interface in a private test copy. Production Oxygen was not upgraded. Check the tested versions below; other versions may use different labels.

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.

  1. Open the page in Oxygen. Add a Text element for the project heading and a short project summary, then choose Add Element and search for Button. Add the Breakdance Button below the summary.
  2. Select the Button. In the Content tab, set Text to “Generate a fluid font size” and Link to https://benjaminolsen.dev/css-clamp-generator/. Use your own real destination on a client project.
  3. Open Design → Button and choose Custom. Open the Custom control. Set Background to #d5ef59.
  4. In Custom → Typography, set Color to #171b19 and Font Size to 18px. Keep one primary call to action; secondary links should compete less visually.
  5. Save and inspect the frontend. In the tested version, the default custom-button padding produced a 48px-high click area with these settings.
  6. Use the keyboard to reach the link. Confirm a visible focus outline, then press Enter and check that the intended tool page opens.
  7. Check at 390px and on desktop. Try a longer label, such as “Generate a fluid font size — see the full guide and practical examples”, and ensure it wraps without horizontal scrolling.
  8. Restore the concise label. Review your own project’s actual copy and destination before publishing.

Call-to-action illustration · HTML/CSS, not an extension demo

A useful next step should describe its destination.

Generate a fluid font size

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 is a conceptual HTML example. You do not need to paste it into Oxygen; use the element’s interface. The tested linked Button rendered an anchor on the frontend. Replace destinations and connect any action to real behavior.

Tested versions and limits

The worked example was recreated through the Oxygen interface on 4 October 2026 with Oxygen 6.2.0-beta.9 and Breakdance Elements for Oxygen 1.1.0-beta.5. Its saved frontend was also checked after switching the private copy to Oxygen 6.2-rc.1. WordPress was 7.1.2 and PHP was 8.5.11. The browser copy used SQLite; no production builder upgrade was performed.

The test confirmed ordinary element insertion, text and link controls, the Custom design controls, the saved frontend, keyboard focus and Enter navigation, a 390px layout, long-label wrapping and reset. The destination opened the actual CSS Clamp Generator. The chosen foreground/background colors have a calculated contrast ratio of 13.52:1; the tested click area was 48px high.

This verifies the described static CTA workflow, not every Button setting or an accessibility audit of your website. Lightbox, icons, actions, animations and dynamically supplied links were not part of this example. A static link has no provider-data empty state; if you later bind a dynamic URL, check missing data separately.

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.

Need more help with this guide? Contact Benjamin →

Explore more topics