Notice Box

Say the one thing the shopper needs to know, where they will see it

A framed message with an icon, in five meanings: a dispatch deadline, a promise about returns, a stock warning, a payment provider that is down. One element, five palettes, and no theme template to edit.

A deadline that is impossible to miss

"Order by 19 December" in an amber frame is read before the paragraph around it. The colour does the work the copy would otherwise have to do.

Objections answered before they form

Free returns, VAT included, dispatch times — the facts a shopper is looking for, in a block that reads as a fact rather than as an advert.

Bad news delivered well

When card payments fail or a courier is on strike, the notice goes up in minutes, on any page, with no developer and no theme change.

Use cases

Where shops put it

Seasonal dispatch deadlines

One warning notice at the top of the basket page in December, taken down in January. The date is copy, not configuration, so anybody in the marketing team can move it.

Category and product caveats

A neutral notice under a product that ships from a second warehouse, or a small one inside a column saying the size runs large. The Small size is made for exactly that.

Service interruptions

An error notice on the checkout page when a payment provider is down, naming the method that still works. It is the one appearance that a screen reader announces immediately.

What you control

Every field in the form, in plain words

Five appearances
Info, Success, Warning, Error and Neutral, each with its own palette and its own fallback icon.
Title and message
The title editable on the stage with a choice of heading tag, the message in the ordinary WYSIWYG editor.
Icon
The glyph that belongs to the appearance, any key from the bundled library, or none at all.
Two sizes
Small for a one-line notice inside a column, Medium for a standalone one.
Accent bar
Down the left edge, shown or hidden.
Your own background and text colours
Over the palette — the icon follows the text colour, so it never disappears on a dark background you chose.
An optional button
With its own text, link and style, or a plain link.
A dismiss button
And an honest note in the form about what it does not do.
Advanced tab
For alignment, spacing, border and CSS classes.

Shown in the demo store

Native and honest

Your content is written in Magento's own format

The notice is stored as a heading, a paragraph and a link — in that order. The instruction that tells a screen reader what kind of block it is travels in the page content, not in our script, so it survives everything.

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_PageBuilder module 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

Does closing a notice make it stay closed?
Can I colour the icon separately?
Why is the Error appearance different from the other four?
What does it look like with the module switched off?

Content blocks

More in Content blocks

Blockquote / Pull Quote

A quotation set apart from the text — beside an accent bar, as a pull quote or on a card.

Data Table

Size charts, spec sheets and price lists, typed straight into the page.

Flip Box

A card with two sides that turns over on a tap, a click or from the keyboard — and on hover.

Icon List

Rows of icon and text, stacked or in a grid of two, three or four.

Image Box

An icon or an image, a heading, copy and an optional button.

Team Members

The people behind the shop in cards or rows — a photo, a name, a job title, a few sentences.

Timeline

A history with dates or a process with numbered steps, down the page or across 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.