Documentation-based practice example; check the controls in your installed Oxygen version.
What it does and when to use it
Include a registered WordPress widget in your Oxygen layout. 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: An existing plugin's sidebar block
Scenario: An existing plugin's sidebar block. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Choose a registered widget from an active plugin that solves an actual sidebar need.
- Add Widget, select that widget and configure its visible settings.
- Preview while logged out and check its heading level, width and plugin styles.
Expected result
You should have an existing plugin's sidebar block. 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 widget is missing from the selector, check that its provider is active and registers a compatible widget. Styling the outer container may not change the widget's internal markup.
Checks before publishing
Widget availability depends on active plugins. Its internal markup and styling may differ from native Oxygen elements.
- 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 Widget 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.