Elements · 35
Thirty-five elements for the native Page Builder
Wrizu Page Builder Extensions adds them to the Page Builder that already ships with Magento 2 — no second editor, no proprietary format, nothing to migrate afterwards. Each one is a native content type, so it drags, previews, aligns and saves exactly like the elements you already use.
Content blocks
8 elements
Layout & navigation
6 elements
Media & motion
7 elements
Conversion & trust
11 elements
Catalogue
3 elements
Catalogue
Two of them read your catalogue
Reads your catalogue
Product Spotlight and Hotspots work differently from the other thirty-three, and the difference is worth stating on the page rather than in the docs alone. A product's name, price and picture are not stored in the page: they are read from the catalogue every time the page is shown. A price changed in the catalogue reaches the landing page, and saving the product clears that page from the cache by itself.
The other side of that trade: those two elements need the module running on the storefront to show a product at all. Without it the product half renders as nothing and what stays is the text the editor wrote. A SKU that matches nothing behaves the same way — no error, no empty box, just the words you typed. We think that is right, because a frozen price is worse than no price; but it is a real difference from the thirty-three elements whose content is entirely yours.
Category Tiles sits in the same group but reads nothing from the catalogue: the picture, the name and the subtitle on a tile are what you upload and type. Only its link knows the catalogue — a category or a product picked from the catalogue tree is stored as a reference, and Magento turns it into the current address every time the page is shown, so a changed URL key does not break the tile.
Three steps, then you are building
01
Install the module
Unpack the ZIP from your licence panel into app/code — the files land in app/code/Wrizu/PageBuilderExtensions/ — then run the Magento commands from the installation guide: module:enable, setup:upgrade, setup:di:compile, the static content deploy and cache:flush. Installing with Composer works too. Nothing in Magento is overridden or replaced.
02
Drag it from the Wrizu panel
Open any page, block or category description with Page Builder and find the new Wrizu section in the left-hand panel, next to the native ones. Drop an element into a Row, a Column or a Tab, exactly as you would a native content type.
03
Configure it
Click the gear icon for the settings form, or type straight onto the stage where a field is editable in place. Alignment, margins, borders and CSS classes come from the native Advanced tab you already know.
Native and honest
Your content is written in Magento's own format
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
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.