Benjamin Olsen
All topics

Guide

Breakdance Menu Button: A prominent secondary action within navigation

A prominent secondary action within navigation. Learn when to use Menu Button, follow a practical setup, and diagnose common problems.

2 min read · Updated 30 September 2026

Practice recipe based on public documentation; the Breakdance extension is not installed here.

What it does and when to use it

Creates a button-style item within a menu. 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 prominent secondary action within navigation

Scenario: A prominent secondary action within navigation. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Use it for a real action such as opening the tools directory or contact page.
  2. Add it inside the matching menu structure and keep its wording distinct from ordinary links.
  3. Check that it fits the mobile menu and retains visible focus.

Expected result

You should have a prominent secondary action within navigation. 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 every navigation item looks like a primary button, reduce the emphasis. Use one prominent action where the hierarchy benefits visitors.

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 Menu 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.

Explore more topics