Documentation-based practice example; check the controls in your installed Oxygen version.
What it does and when to use it
Edit a continuous block of article content with formatting controls. 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 tutorial body that editors can maintain
Scenario: A tutorial body that editors can maintain. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Use a single Rich Text block for the flowing tutorial body.
- Add an introduction, two H2 sections, an ordered procedure and a descriptive link.
- Preview the frontend and check that lists, code and headings have readable spacing.
Expected result
You should have a tutorial body that editors can maintain. 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 a layout needs independent columns or reusable cards, build those with native containers and text. Rich Text is a prose editor, not a page-layout system.
Checks before publishing
Use regular Text and Containers for page layouts. Rich Text is best for prose rather than a whole homepage.
- 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 Rich Text Element 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.