All topics

Guide

Breakdance Progress Bar: A labelled percentage from a real process

A labelled percentage from a real process. Learn when to use Progress Bar, follow a practical setup, and diagnose common problems.

3 min read · Updated 4 October 2026

The worked example was recreated through Oxygen’s interface and checked on the frontend on 4 October 2026. See the tested versions below.

What it does and when to use it

Displays a labelled value as a horizontal progress indicator. 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 was recreated in a private Oxygen test copy. Exact labels may differ in another version. Production Oxygen was not upgraded.

Worked example: A labelled percentage from a real process

Scenario: A labelled percentage from a real process. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Use a defined quantity, such as a launch checklist with 12 tasks. Six completed tasks correspond to 50%; do not present a subjective skill score as measured progress.
  2. In Oxygen, choose Add Element and search for Progress Bar. Add the Breakdance element to the page.
  3. Select it and open the Content tab. Set Progress to 50 and Title Text to “Launch checklist: 6 of 12 tasks complete”. Leave Hide Percentage off so the number remains visible.
  4. Save and inspect the frontend. Confirm that the title, 50% label and visual bar agree.
  5. Try Progress 0 with “Launch checklist: Not started”, then 100 with “Launch checklist: 12 of 12 tasks complete”. Save and inspect each state. Restore 50 and the original title afterwards.
  6. Try a longer title and inspect the page at 390px and on desktop. The label must remain readable and the page must not scroll horizontally.

Tested versions and limits

Recreated on 4 October 2026 with Oxygen 6.2.0-beta.9 and Breakdance Elements for Oxygen 1.1.0-beta.5, WordPress 7.1.2 and PHP 8.5.11. The saved frontend and zero/partial states were also checked on a private Oxygen 6.2-rc.1 copy. Browser testing used SQLite; production was not upgraded.

The test used normal element insertion through Add Element, Progress and Title Text controls, visible percentages, saved values 0, 1, 50 and 100, a long title, and a 390px viewport without horizontal overflow. Zero was saved and rendered through the actual builder in both tested Oxygen versions.

The earlier note that zero was unavailable was based on a restriction in the MCP editing tool, not the builder interface. When following this guide, use Oxygen’s controls. A static progress indicator is not an interactive control to tab through; keep a meaningful text label visible. Dynamic progress, scroll animation and all design options were outside this example.

Expected result

You should have a labelled percentage from a real process. 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 value is a subjective skill rating, explain its basis or use descriptive text. Avoid presenting arbitrary percentages as measured proficiency.

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 Progress Bar 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