All topics

Guide

Oxygen 6 Component: A reusable guide card

A reusable guide card. Learn when to use Component, follow a practical setup, and diagnose common problems.

2 min read · Updated 30 September 2026

Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.

What it does and when to use it

Reuse a centrally maintained design in multiple places. This example focuses on one achievable outcome rather than listing every possible setting.

Before you start

Start with a test page and the data or assets described in the example. The values below are starting points, not universal design defaults.

Worked example: A reusable guide card

Scenario: A reusable guide card. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Create a guide card with Containers, Text and a Text Link. Keep its spacing and typography in shared classes.
  2. Turn the card into a reusable Component using Oxygen’s component workflow. Expose only the content that should vary between cards.
  3. Insert it in two places and change the title and destination for each instance. Edit the Component to make a shared design change.
  4. Check both instances on the frontend. For post loops, bind instance content to the current post rather than hardcoding one title or URL.

Expected result

You should have a reusable guide card. 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 instance repeats identical text, separate shared design from instance data. Use dynamic fields or supported editable properties for the values that differ.

Checks before publishing

Bind per-post values dynamically in repeated items. Use editable properties when instances need controlled differences.

  • 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 Component reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.

The native references were checked against the site’s Oxygen 6.2.0-beta.9 installation and public documentation. Individual recipes should still be validated in your project.

Need more help with this guide? Contact Benjamin →

Explore more topics