Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.
What it does and when to use it
Swiper is the slider element registered in this site’s Oxygen 6.2 beta build. It can use static child slides or an image collection. Its controls include navigation, pagination, touch behavior, responsive slide counts and accessibility messages. 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 manual project showcase with two slides
Scenario: A manual project showcase with two slides. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Add Swiper to a test page and create two Swiper Slide children. Place a screenshot and descriptive text in each.
- Configure slide spacing and navigation through Swiper’s controls. Start with autoplay off so visitors can read each slide.
- Choose a phone breakpoint with one readable slide at a time. Ensure long text fits and controls remain visible.
- Test navigation and any keyboard controls on the frontend. If the slides are essential content, make sure visitors can reach them without relying only on automatic motion.
Expected result
You should have a manual project showcase with two slides. 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 content is clipped, inspect the slide's own width and height as well as the parent. A simple grid is easier to scan when visitors need to compare every project.
Checks before publishing
Use real text and assets rather than a perfect placeholder. Check a long label, narrow screen and empty-data state before publishing.
- 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 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.