Accordion
Answer the question where it is asked, not on a policy page
Collapsible panels that put delivery, returns and sizing on the product page without burying it in text. Each panel holds real Page Builder content — a paragraph, a list, an image, a button — and the whole block can publish itself to Google as an FAQ.
The default appearance, one panel open, a paragraph, a list and a button inside it.
Fewer questions reaching support
The answers a shopper would have emailed you sit one click from the Add to basket button. Nothing leaves the page, so nothing interrupts the purchase.
An FAQ Google can read
One switch publishes the questions and answers as FAQPage structured data. It is off by default, because that markup is a promise about your own content rather than a decoration.
A panel takes anything, not just text
Drop an image, a button, a list or another Wrizu element into a panel. It is a Page Builder container, so the content inside it has its own settings forms.
Use cases
Where shops put it
Delivery, returns and sizing on a product page
Three panels under the Add to basket button, each answering the objection that otherwise ends in an abandoned basket. The first one opens on arrival, so the block never looks like three dead lines.
A category description that has to be on the page
The copy your search team wants lives in a panel with a heading the shopper can ignore. The text is in the page for a crawler either way, closed or open.
Terms, warranty and small print
The Minimal appearance turns four legal sections into four quiet lines at the foot of a page, with an anchor on each — so a link in an email can open exactly the one you meant.
- Three appearances
- Default (hairlines between items), Boxed (a card per item) or Minimal (no frames at all).
- One panel at a time, or several at once
- And whether the first one opens on arrival.
- Indicator
- A chevron that rotates, or a plus that turns into a minus.
- Heading size
- In three steps, and an accent colour that reaches the open heading, its indicator and the border of an open card.
- Search engine markup
- None, or FAQPage.
- Per item
- The question, the heading tag (H3, H4 or a plain container), an optional icon from the bundled library, "open by default", and an anchor that makes a link open that panel.
- Anything inside a panel
- Text, headings, images, buttons, dividers, video, banners, sliders, maps, product lists and every Wrizu element.
- Advanced tab
- On the accordion and on each item.
Shown in the demo store
Boxed with two panels open at once, and Minimal with plus indicators.
Nothing open on arrival, one item opening itself, and an anchor on another.
The variant that publishes FAQPage structured data.
Native and honest
Your content is written in Magento's own format
A panel is a real Page Builder container, so what you put inside it is stored as its own content type — a paragraph stays a paragraph, an image stays an image. The questions are real headings and the toggles are real buttons, which is why the keyboard works without a setting.
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
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.
Content Slider
A carousel whose slides hold any content — one to six on screen, with a pause button.
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.