Installing Hyvä on Magento 2 and Mage-OS

Before you start

Hyvä does not load RequireJS, Knockout or jQuery. Every extension that adds frontend code the Luma way stops working until it is adapted. So the first job is an inventory, not an install.

• List every enabled module with a view/frontend folder.
• For each one, check whether a Hyvä version or a compatibility module exists.
• Mark what you will adapt yourself and what you can switch off.

Our articles Hyvä migration checklist and extensions without a compatibility module go through this in detail.

Requirements

Installing with Composer

Hyvä packages come from Hyvä's own Packagist repository. Add your key and repository URL from your hyva.io account, then require the theme:

composer config --auth http-basic.hyva-themes.repo.packagist.com token YOUR_KEY
composer config repositories.private-packagist composer https://hyva-themes.repo.packagist.com/YOUR_PROJECT/

composer require hyva-themes/magento2-default-theme
bin/magento setup:upgrade
bin/magento hyva:config:generate

hyva:config:generate tells the Tailwind build where module templates are. Run it again whenever you add or remove a Hyvä-aware module.

Creating a child theme

Never edit Hyva/default directly; updates would overwrite your work. Create a child theme:

app/design/frontend/Vendor/hyva/
  registration.php
  theme.xml              # <parent>Hyva/default</parent>
  web/tailwind/          # copied from vendor/hyva-themes/magento2-default-theme/web/tailwind

cd app/design/frontend/Vendor/hyva/web/tailwind
npm ci
npm run build

Then assign the theme in Content › Design › Configuration. Our child theme guide covers the structure in more depth.

Settings after switching

• Turn off Magento's JavaScript bundling, merging and minification for the Hyvä store view; Hyvä does not use them.
• Turn off CSS minification too; the Tailwind build is already minified.
• Run in production mode and deploy static content for every locale you sell in.
• After each deploy, check that pub/static/deployed_version.txt holds only the version number, without a trailing newline. A newline breaks the theme path, and add to cart, search and the cart drawer stop working together.

What to test before go-live

• Add to cart from category pages, product pages and quick view.
• Login, registration, password reset, contact and newsletter forms, with reCAPTCHA switched on as it will be live. Forms copied from Luma often miss the form_key.
• Checkout with every payment method, including the return from the payment provider.
• Analytics events: page views, add_to_cart, begin_checkout and purchase.
• Mobile pages with Lighthouse, on a real phone as well as in the browser.

Hyvä in Türkiye and across Europe

MageBooster is a Magento team with offices in Tallinn (Estonia) and Istanbul (Türkiye). We work with stores across Europe and in Türkiye, in English, German and Turkish. You talk to the people who do the work: the same team plans, installs and looks after your store.

How a project runs

Work happens remotely with screen-sharing calls; you keep full access to your code and server at every step. Our working hours are Monday to Friday, 09:00 to 18:00 Istanbul time.

MageBooster Checkout

Many stores lose the most customers at checkout. Next to installations we build and install MageBooster Checkout, our own Hyvä checkout. It runs on Magento 2.4.9 and Mage-OS and comes in four layouts for international stores, from a single page to a guided multi-step flow.

• Address, shipping and payment on one screen, or in steps, depending on the layout you choose.
• Payment methods your country expects, including installment payments for stores in Türkiye.
• Built with Alpine.js and Tailwind CSS like the rest of Hyvä, without the Luma checkout's JavaScript.

You can try it on our demo store at demo.magebooster.com. No real orders are placed there.

Need help?

We install Hyvä, adapt extensions and look after Hyvä stores in Türkiye, Germany, the UK and across Europe.