Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.
What it does and when to use it
Make an entire group of content one clickable link. 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 project card with one destination
Scenario: A project card with one destination. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Add Container Link and choose one project detail page as its destination in the link controls.
- Add an Image, a title and a short summary inside it. Do not place another link or button inside the linked card.
- Select a shared class for spacing and appearance. Configure a visible focus style so keyboard users can identify the whole card.
- Preview the frontend, press Tab to reach the card and Enter to follow its destination. Check it with a long title on a phone.
Live linked-card illustration · HTML/CSS
CSS Clamp GeneratorOpen the real tool. This entire card has one destination.
Use the Oxygen interface
Select the element or its parent Container, choose the intended shared class, and configure layout, spacing and typography in the builder. Switch to a narrower breakpoint to make responsive overrides. You do not need to paste CSS for this example.
Expected result
You should have a project card with one destination. 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 card contains another anchor, split the actions into separate containers. A clickable card should have one clear destination, not competing nested links.
Checks before publishing
Nested links are invalid HTML. Keep the label meaningful and provide a visible keyboard focus state.
- 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 Container Link 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.