Practice recipe based on public documentation; the Breakdance extension is not installed here.
What it does and when to use it
Places the individual page body inside a shared template. 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 shared template around individual page bodies
Scenario: A shared template around individual page bodies. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Build the reusable navigation and main wrapper in a template.
- Place the content area where each page's unique body should appear.
- Apply the template to two pages and confirm that their own content changes.
Expected result
You should have a shared template around individual page bodies. 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 content repeats across every page, check whether it was entered in the template instead of the pages. Prefer Oxygen's native equivalent when it fits the same purpose.
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 Template Content Area 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.