Practice recipe based on public documentation; the Breakdance extension is not installed here.
What it does and when to use it
Styles two parts of a heading independently. 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 two-part heading with one readable meaning
Scenario: A two-part heading with one readable meaning. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Write a heading whose parts form one sentence.
- Use the visual distinction to emphasize a word rather than hiding essential meaning in color.
- Choose a single appropriate heading level and check line wrapping.
Expected result
You should have a two-part heading with one readable meaning. 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 second part wraps awkwardly, shorten the heading or reduce visual contrast between the parts. Do not create two separate H1 headings for one title.
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 Dual Heading 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.