Show More
Keep the copy your search team wants, without giving it the first screen
Show More clips a block to the height you choose and puts a toggle under it. The whole text stays in the page — for a crawler and for a screen reader — while a shopper sees the products instead.
A long description collapsed to 240 px with the white fade.
The SEO copy and the shopper stop competing
The description is in the page in full, clipped rather than hidden, so nothing is removed from what a crawler or a screen reader reads.
No jump when the page loads
The clipping is done by the stylesheet, not by a script running after the paint — so the page does not show two thousand pixels of text and then fold them away.
It decides for itself when a toggle is pointless
The element measures its own content. Shorter than the threshold and it stays open with no button at all, on a desktop and on a phone independently.
Use cases
Where shops put it
Category description under the product grid
Four paragraphs of copy collapsed to 240 px at the foot of a category page. The grid keeps the screen; the text keeps its place in the page.
Long specifications on a product page
A full technical specification clipped to a few lines, with "Show the full specification" as the label. Anything goes inside — a table of text, an image, a downloadable spec sheet behind a button.
Terms, care instructions and small print
The paragraphs that have to be somewhere but should not be the first thing anyone reads, on a tinted section with the fade colour matched to it.
- Collapsed height in pixels
- And content shorter than it gets no button at all.
- Start collapsed or expanded
- Expanded is useful where the block should open by default but still be foldable.
- Fade out
- Shown or hidden, with a colour of its own so the gradient matches a tinted section instead of leaving a white mist.
- Both labels
- "Show more" and "Show less" are defaults you can replace with anything.
- Button style and alignment
- Primary, Secondary or a plain link, on the left, centred or on the right.
- Anything inside
- Text, headings, images, buttons, dividers, video, banners, sliders, maps, product lists and every Wrizu element, the Accordion included.
- Advanced tab
- For alignment, spacing, border and CSS classes.
Shown in the demo store
Content shorter than the height and no button, and an Image Box dropped inside another block.
Started expanded with its own labels, and a tinted fade at 120 px.
Two columns, one with the fade switched off and one with it kept.
Native and honest
Your content is written in Magento's own format
Clipped content is never display: none. It is cut with a maximum height, so everything reading the page has all of it, whatever state the block is in. That is the whole reason to use this element rather than to delete the copy.
One thing we will not pretend about: if the stylesheet loads and the script does not — a script error, a blocked request — the content stays clipped with nothing to expand it. It is still in the page for a crawler and a screen reader, but a sighted visitor with a mouse will not see it. We took that trade deliberately: the alternative is a page that jumps on every single visit.
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.
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.
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.