Documentation-based practice example; check the controls in your installed Oxygen version.
What it does and when to use it
Swiper Slide is an individual slide inside the Swiper parent. It is a content container rather than a second standalone slider. 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: One slide in a project carousel
Scenario: One slide in a project carousel. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Add this child inside its matching Swiper parent.
- Put one project heading, image and link in the slide, using the same content order in every slide.
- Change slides through the parent's controls and check that links remain reachable.
Expected result
You should have one slide in a project carousel. 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 slide does not participate in navigation, verify its parent structure. Avoid placing a standalone slide on the page and expecting it to supply carousel controls.
Checks before publishing
Keep slides inside their matching parent. Configure slide counts, navigation and playback on the parent Swiper, not by treating every slide as a separate carousel. Check the mobile layout and keyboard 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 Swiper Slide 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.