Icon List
The list shoppers actually scan
Rows of icon and text for features, benefits or steps — stacked in a column, or spread across a grid of two, three or four. Each row is its own item, so you build the list by dragging rather than by formatting a paragraph.
The vertical layout with separators, three icon sizes and per-row colours.
Use cases
Where shops put it
What is included
On a product or bundle landing page, a vertical list of what comes in the box, each row with a tick, each optionally linked to the page that explains it.
Delivery and returns, summarised
In a category description: four rows with a truck, a clock, a refresh and a shield. Shorter than a policy page and read far more often.
Service promises across the home page
A three-column grid under the hero — support hours, payment methods, warranty — where a vertical list would be too tall and a paragraph too easy to skip.
- Layout
- Vertical, or a grid of 2, 3 or 4 columns.
- Spacing between rows
- S, M or L.
- Separator lines
- Between rows, in the vertical layout.
- Icon size
- S, M or L (16, 24 or 32 px), which also sets the gap to the text.
- Text colour
- For the whole list; icons inherit it unless a row sets its own.
- Per row
- An icon from the 24 bundled with the module, its own icon colour, the text, and an optional link — URL, CMS page, category or product — that makes the whole row clickable.
- Advanced tab per row
- Margins, border, alignment and CSS classes.
Shown in the demo store
The same list as a grid of three.
Grids of two and of four columns.
Native and honest
Your content is written in Magento's own format
What the Icon List stores is a real <ul> with <li> items — a list to a browser, to a screen reader and to anything else that reads your page.
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
Content blocks
More in Content blocks
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.