All topics

Guide

Breakdance Image: A project image that supports the adjacent copy

A project image that supports the adjacent copy. Learn when to use Image, follow a practical setup, and diagnose common problems.

3 min read · Updated 4 October 2026

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

What it does and when to use it

Displays an image. 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.

Use the native Oxygen element in this version

The legacy Breakdance element described by this catalogue entry was not registered under that name in the installed Oxygen 6.2.0-beta.9 and Elements 1.1.0-beta.5 test library. Use Oxygen’s Image element for this task. Its controls can differ from the original Breakdance element. Read the native Oxygen guide.

This availability check does not mean the full recipe has been practically verified. Prefer Oxygen’s interface when configuring the replacement.

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 image that supports the adjacent copy

Scenario: A project image that supports the adjacent copy. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Select a permitted, optimized image.
  2. Add meaningful alt text when it conveys information and choose a crop that preserves the important subject.
  3. Check the image at the page's actual rendered width.

Expected result

You should have a project image that supports the adjacent copy. 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 asset becomes blurry, use a suitably sized source. If it crops an interface label, preserve its natural ratio rather than treating it as decoration.

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 Image 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