Content Slider
More in one row, and nothing the shopper cannot stop
A carousel whose slides hold real Page Builder content: headings, text, buttons, pictures and other Wrizu elements. One to six slides on screen, set separately for desktop, tablet and phone, with a visible pause button whenever it moves on its own.
Cards, three at a time, with arrows, dots and the Pause button.
A slide is a container, not a text field
Build each slide from the elements you already use: a heading and a button, an Image Box, a Notice Box, a photograph with words over it. Everything inside keeps its own settings form.
A carousel a visitor can stop
Whenever the slider plays on its own, a Pause button sits under the slides. WCAG 2.2.2 asks for that control, and Page Builder's own slider does not have one. A visitor who asks their system for reduced motion never gets autoplay at all.
Nothing jumps while the page loads
The row is laid out at its final widths before the carousel script arrives, with room kept for the arrows, the dots and the pause button. The content under the slider stays where it is when the script starts.
Use cases
Where shops put it
Delivery, returns and payment promises on the home page
Five short cards, three at a time on a desktop and one on a phone, instead of a row of columns that wraps onto a second line.
A hero that rotates between campaigns
One slide at a time with a fade, each on its own photograph with its own heading and button. The Pause button lets a shopper stay on the offer they were reading.
Mixed content on a landing page
An Image Box in one slide, a Notice Box in the next, a plain heading and paragraph in the third. Two at a time, with arrows and no looping, so the reader knows where the set ends.
- Visible slides per screen
- 1 To 6 on desktop, 1 to 4 on tablet, 1 or 2 on a phone. With fewer slides than places, the slides share the row instead of leaving gaps.
- How far one step moves
- One slide, or a whole screenful.
- Navigation
- Arrows, dots, both or none, with looping on or off.
- Slide or fade
- . The fade is offered where one slide is on screen at a time.
- Autoplay, its interval and pause on hover
- Plus the Pause button and the words on it.
- Two appearances
- Slides as you built them, or every slide drawn as a card. Spacing between slides and equal heights are yours to choose.
- Per slide
- A background colour or picture, a text colour, a minimum height and where the content sits inside it.
Shown in the demo store
Cards moving on by autoplay, then Pause pressed: the button turns to Play and the slides stay put.
One slide at a time with a fade, on photographs.
An Image Box and a Notice Box in two slides, arrows only.
Two slides sharing a row set for four.
Native and honest
Your content is written in Magento's own format
Each slide is stored as an ordinary section holding ordinary content types, in your order. Only the visitor's browser turns them into a carousel. With the module switched off, the slides read as sections of the page, one under another, with their backgrounds still in place.
Where the promise stops: with looping on, the carousel copies slides at both ends of the row so it can wrap around, and a copy of an accordion or a popup trigger behaves as a copy. For slides with interactive content, switch looping off. The docs say so, and so do we here.
Every element saves itself the way native Page Builder saves its own: a plain <div data-content-type="wrizu_…"> with its settings in data-* attributes, stored with the page. There is no proprietary database table, no shortcode, no second editor and nothing that has to be converted later.
That has a practical consequence. Disable the module and the storefront keeps serving those pages: headings, copy, images, links and buttons stay visible and clickable, and the styling you set per element — alignment, colours, spacing — stays with them, because it lives in a <style> block stored with the page rather than in our stylesheets. What you lose is what our CSS draws: the layouts, the borders and shadows, the button variants and the bundled icons.
One honest warning
With the module switched off, do not open and save a page that contains Wrizu elements — Page Builder flattens any page holding a content type it does not know into a single HTML Code block, and that save cannot be undone. It behaves that way with every unknown content type, not only with ours, and the storefront is unaffected either way; the rule is simply to leave those pages alone until the module is back on.
Works with any Luma-based theme
The elements are built on the same front-end stack the native Page Builder uses: jQuery and the libraries Page Builder already loads. They target Luma-based themes — Magento Blank, Luma, and the custom themes shops build on either of them.
Buttons use Luma's own button mixins, so a Wrizu button looks like a button from your theme rather than like a button from a plug-in. All of the module's CSS is scoped to [data-content-type^="wrizu_"], so it styles our elements and nothing else in your theme.
Requirements
- Magento Open Source or Adobe Commerce 2.4.6 or newer, with the
Magento_PageBuildermodule enabled - PHP 8.1 to 8.5 — whichever your Magento version supports
- No other extension, no external icon font, no CDN dependency
Questions about this element
Layout & navigation
More in Layout & navigation
Accordion
Collapsible panels, each holding real Page Builder content.
Advanced Tabs
Tabs across the top or down the side, with icons, each tab holding any content.
Anchor / Section Link
A named place on a page — #delivery, #size-guide — that a menu, a list or an e-mail can link to.
Shape Divider
Seven decorative edges between two sections, drawn as inline SVG.
Show More
A block clipped to a chosen height, with a toggle under it.
Thirty-five conversion elements for the Page Builder you already have
Wrizu Page Builder Extensions adds them to the native Magento 2 Page Builder — no second editor, no proprietary format, no content held hostage.