Does Hyvä work with Magento Page Builder?
Yes, Hyvä works with Magento Page Builder. Hyvä Theme bundles Page Builder compatibility in its theme module. Existing CMS pages built with native Page Builder elements keep rendering after a Luma migration. Problems usually start with extension content types and the slider rewrite in Hyvä 1.4.0.
Quick answer
Hyvä Theme renders native Magento Page Builder rows, columns, banners, sliders and product grids without any add-on module. Third-party content types that add storefront output still need a Hyvä compatibility module. For a live visual editor, Hyvä CMS can replace Page Builder one page or block at a time. Hyvä CMS ships with Hyvä Commerce at €3,000 per year.
How Hyvä renders Magento Page Builder content
Page Builder’s default storefront output relies on Luma’s RequireJS and jQuery widgets. Those are gone on Hyvä, so the theme rebuilds that layer in Alpine.js and Tailwind CSS.
John Hughes of FishEye built the original compatibility module while Page Builder was still exclusive to Adobe Commerce. After Page Builder became part of Magento Open Source in version 2.4.3, Hyvä merged that module into the theme module.
Under Stores > Configuration > Hyvä Themes, a Page Builder setting lazy-loads background images. It’s off by default and needs the Hyvä default theme 1.3.10 or later, per the Hyvä theme settings reference.
In Hyvä 1.4.0, one Alpine plugin replaced the Glider.js Page Builder slider and now drives every slider in the theme. Want the old slider back? The 1.4.0 upgrade notes list three files to copy into your theme.
What needs extra work with Magento Page Builder on Hyvä?
- Extensions that add a storefront content type, such as an accordion, ship Luma frontend code. Each needs a Hyvä compatibility module, which some vendors publish as a separate Hyvä package.
- Admin-only Page Builder tools that never touch the storefront need no Hyvä compatibility module.
- Custom content types your team built for Luma also need rebuilding for Hyvä. Plan one Hyvä template and one Alpine component per type.
- Some third-party drag-and-drop builders don’t support Hyvä at all. Check the vendor’s Hyvä compatibility statement before replacing Page Builder with one.
- The admin editor stage doesn’t load your Hyvä Tailwind build, so editors see an approximation rather than the real storefront.
- Hyvä versions before 1.3.10 broke the admin preview of product carousels and grids. Update Hyvä to 1.3.10 or later if editors report broken previews.
Before you upgrade Hyvä or remove Page Builder
- Test every Page Builder slider after moving to Hyvä 1.4.0, since the slider markup and behaviour changed.
- Don’t strip
magento/module-page-builderout with a composer replace rule. Hyvä’s 1.3.10 notes warn this breaks static content compilation. Keep it installed and runbin/magento module:disableinstead. - For each Page Builder extension, check the Hyvä Compatibility Module Tracker and the vendor’s changelog before launch.
Page Builder or Hyvä CMS: which should you use?
If your editors are comfortable in Page Builder, nothing forces a switch. Hyvä Theme is free and keeps supporting it.
The alternative to Page Builder is Hyvä CMS. Its Liveview editor previews edits on the real storefront while you build. It also keeps drafts and version history.
| Magento Page Builder | Hyvä CMS | |
|---|---|---|
| Cost | Included with Magento Open Source 2.4.3+ and Adobe Commerce 2.4.x | Part of Hyvä Commerce, €3,000 per year |
| Where you preview edits | Admin editor stage | Liveview, on the real storefront |
| Scheduled publishing | Adobe Commerce only, through Content Staging | Built in |
| Rollout | Enabled by default for CMS pages and blocks | Opt in per CMS page or block |
| Adobe Commerce stores | Supported | Through Hyvä Enterprise: €7,500 first year, then €5,000 a year |
Moving from Page Builder to Hyvä CMS is gradual. According to Hyvä’s FAQ, installing Hyvä CMS leaves existing Page Builder output untouched. You can also migrate Page Builder content into Hyvä CMS.
For most Luma to Hyvä migrations, keep Page Builder through launch and audit custom and third-party content types first. Revisit Hyvä CMS if editors keep finding that published pages look different from the admin preview. Planning the move? See how we approach Hyvä theme development.
Related Answers
Still need help?
Talk to our Hyvä experts
Not sure how your Page Builder pages will behave on Hyvä? We can review your content types and extensions before you migrate.