Team Members
Put a face and a direct line on every name
The people behind your shop in cards or in rows: a photo, a name, a job title, a few sentences, and an e-mail address, a phone number and a link that work the moment a visitor taps them.
Three across, round photos, every kind of contact.
People buy from people
A buyer who can see who answers the phone trusts the shop more than one who reads "contact us". A name and a photo turn a faceless store into a team.
One tap to reach the right person
The e-mail opens the mail program with the address filled in. The phone number dials on a phone. What the visitor reads is exactly what you typed, extension and all.
Built in minutes, kept in order by dragging
Add a person from the team's menu, type the name and the job title straight onto the page, and reorder people by dragging. The photos keep one shape and one size across the whole team.
Use cases
Where shops put it
An "About us" page
The founders and the team three or four across, each with a round photo, a job title and two sentences about what they do.
Shops and account managers
One person per row with the photo beside the words: each branch manager with the shop's phone and e-mail, or each trade account manager with a link to book a call.
Experts next to the products
A size advisor or a bike fitter beside the range they know, with a link to the booking page, so the question goes to the person who can answer it.
- Two appearances
- Cards in columns (two to five on a desktop, set separately for tablet and phone), or one person per row with the photo beside the words.
- Cards
- None, a thin border or a white card with a soft shadow, with three gap sizes.
- Photos
- Round, rounded or square, in three sizes, cropped to keep the face.
- Names and parts
- Names as H3, H4 or plain text; job titles, bios and contacts each switched on or off without losing what was typed.
- Contacts
- An e-mail address, a phone number and a link to any page, category, product or address, shown as icons with words or as a row of round icon buttons.
- One accent colour
- For the job titles, the icons and the focus ring.
Shown in the demo store
Four across in bordered cards, contacts as icons only, a navy accent.
One person per row, square photos beside the words, cards with a shadow.
The list and the cards on a phone.
Native and honest
Your content is written in Magento's own format
The team is stored as a plain list of people. The e-mail and phone contacts are ordinary mailto: and tel: links, and the address the visitor reads is the one you typed. With the module switched off, the page still shows every person with a heading, a photo and working links; only the columns, the cards and the icons go. There are no brand icons for social networks, because those are other companies' trademarks: a row of social profiles is the Logo Cloud's Social Icons appearance, with marks you upload yourself.
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
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.
Notice Box
A framed message with an icon, in one of five meanings.
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.