Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.
What it does and when to use it
Wrap child elements inside a shortcode that has opening and closing tags. 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 plugin-provided wrapper around a content group
Scenario: A plugin-provided wrapper around a content group. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Choose a documented enclosing shortcode from an active plugin. Confirm that it accepts inner content.
- Add Container Shortcode and supply the enclosing shortcode in its content controls. Add a small content group inside it.
- Use the parent and child layout controls to arrange the visible content; the shortcode provider determines its rendered wrapper.
- Check the frontend with the provider active. Use ordinary Shortcode for output-only shortcodes that do not accept enclosed content.
Expected result
You should have a plugin-provided wrapper around a content group. 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 shortcode prints literally, confirm its spelling and provider. Do not assume a wrapper supplies secure access control; follow the plugin's actual authorization behavior.
Checks before publishing
The shortcode must exist and support enclosed content. Preview with the appropriate user or post context.
- 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 Shortcode 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.