Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.
What it does and when to use it
Link a short text label to another page, file or destination. 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 useful next-step link below a tutorial
Scenario: A useful next-step link below a tutorial. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Add Text Link below the tutorial and choose the destination in its link control.
- Use a descriptive label such as Open the spacing generator. Keep ordinary internal links in the same tab.
- Set readable text styling and a visible focus state through the interface.
- Use Tab and Enter on the frontend. Confirm that the link reaches the correct guide or tool; use a button for an action rather than navigation.
Expected result
You should have a useful next-step link below a tutorial. 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 label makes no sense out of context, include the destination or task. Use a real button for an action such as copying a result.
Checks before publishing
Avoid vague click-here labels. Use a button for an action and a link for navigation.
- 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 Text 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.