Page 4 - Hyvä

A cookie banner that enables Google Tag Manager through an inline script immediately violates the Content-Security-Policy in a Hyvä theme and gets silently blocked by the browser. This article shows how to build a cookie consent module in the Hyvä theme that satisfies both GDPR requirements and CSP restrictions at once, without nonce violations and without loading third-party scripts before consent is given.

Copying Luma's newsletter widget straight into a Hyvä theme collides with the strict Content Security Policy and produces a form that silently fails in the browser. A clean newsletter integration instead needs registerInlineScript(), a lean Alpine.js component with fetch(), a properly communicated double opt-in flow, and a server-validated GDPR consent checkbox, placed cleanly via layout XML in the footer, checkout success page and CMS block.

Wishlist functionality in the Hyvä Theme replaces Magento's Luma widgets with plain phtml and Alpine.js: an Alpine.store holds the product IDs of the saved list on the client, while fetch() calls against the Magento_Wishlist controller with form_key keep the server side in sync. This article shows how the heart icon reacts instantly to clicks, how optimistic updates with rollback work, and how guests are guided cleanly to login without a single page ever fully reloading.

Anyone integrating a third-party module into a Hyva theme sooner or later runs into the module-config.json file. It decides, per module, whether native Hyva templates apply or whether the frontend output falls back to a fallback theme like Magento/blank. This article explains the structure, runtime logic, merge behavior, and custom entries of module-config.json step by step.

Anyone who builds a custom Hyva theme from scratch, rather than inheriting the Hyva Default Theme as parent, gains full control over every line of markup and Tailwind class, but gives up fallback templates that would otherwise kick in automatically.

Not every compatibility module deserves a place in production. Anyone who enables Luma fallbacks blindly instead of auditing them deliberately pays with load time, CSP violations, and unnecessary maintenance effort for rendering paths that no customer ever sees.

The order success page is the moment with the highest attention throughout the entire checkout: the customer has just made a purchase but is still on the page. Anyone who uses this moment for conversion tracking, cross-sell, and customer retention, without Knockout.js, jQuery, or UI components, but with clean Hyvä patterns built from ViewModels, layout XML, and Alpine.js, gets noticeably more out of the order success page than with the standard Luma output.

Anyone migrating from Luma to Hyvä inevitably runs into Knockout-based UI components: jsLayout XML, ko templates and RequireJS modules that Magento has used for years to power dynamic storefront widgets. This guide shows how to read existing UI components, understand their logic and systematically replace them with native Hyvä templates using Alpine.js, including worked examples, a third-party strategy and a rollout checklist for larger stores.

Anyone building a custom contact, quote request or newsletter form in a Hyvä theme regularly forgets one single, inconspicuous hidden field, then wonders about error messages that look like a bug. This article shows how form key CSRF protection works under the hood in Magento and how to wire it up cleanly in phtml templates, AJAX requests with Alpine.js, custom controllers and alongside full page cache, with real code examples from Magento 2.4.8-p4 and PHP 8.4.

Anyone who writes business logic directly into block classes ends up with Magento templates that can neither be tested in isolation nor reused cleanly. The Hyvä ViewModel pattern strictly separates data preparation from presentation, makes every rule verifiable as a plain PHP class with PHPUnit, and keeps phtml templates limited to pure output.