{"id":2174,"date":"2026-09-02T14:14:40","date_gmt":"2026-09-02T08:44:40","guid":{"rendered":"https:\/\/magecurious.com\/blog\/?p=2174"},"modified":"2026-09-07T16:56:34","modified_gmt":"2026-09-07T11:26:34","slug":"hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know","status":"publish","type":"post","link":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/","title":{"rendered":"Hyv\u00e4 Theme Removes the Reset Theme: What Magento 2 Developers Need to Know\u00a0"},"content":{"rendered":"\n<h2>Introduction<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The traditional Hyv\u00e4 reset architecture has been an important part of Magento 2 frontend development for older Hyv\u00e4 projects. As Hyv\u00e4 has evolved, the way Magento layout resets are handled has changed significantly. Newer Hyv\u00e4 Theme versions no longer use the traditional reset-theme parent, introducing a more modern generated base layout reset architecture.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As Hyv\u00e4 continues to evolve, some important architectural changes have been introduced in recent releases. One of the changes Magento 2 developers should understand is the move away from the traditional Hyv\u00e4 reset-theme approach.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For businesses planning a modern Magento 2 storefront, <a href=\"https:\/\/magecurious.com\/hyva-magento2-development\">Hyv\u00e4 development<\/a> can provide a faster and more maintainable frontend architecture.\n<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you&nbsp;maintain&nbsp;an older&nbsp;Hyv\u00e4&nbsp;project, you may be familiar with:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">hyva-themes\/magento2-reset-theme&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and a custom theme that uses:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&lt;<strong>parent<\/strong>&gt;Hyva\/reset&lt;\/<strong>parent<\/strong>&gt;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, this is no longer the architecture used by newer Hyv\u00e4 Theme versions. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Since Hyv\u00e4 Theme 1.3.18, the Hyv\u00e4 Theme no longer uses a reset-theme parent.<br>Hyv\u00e4 1.3.21 introduced the Generated Base Layout Reset module, providing a newer approach to handling Magento\u2019s base layout. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This article explains what changed, why Hyv\u00e4 made this change, what it means for existing Magento 2 projects, and what extension developers should consider when making their modules Hyv\u00e4-compatible. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Was the Hyv\u00e4 Reset Architecture?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Magento 2 comes with a large amount of frontend functionality designed around the traditional Magento\/Luma architecture.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4 takes a fundamentally different approach. It replaces much of the traditional frontend stack with a lightweight architecture based primarily on:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Alpine.js&nbsp;<\/li>\n\n\n\n<li>Tailwind CSS&nbsp;<\/li>\n\n\n\n<li>PHP templates&nbsp;<\/li>\n\n\n\n<li>Magento layout XML&nbsp;<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The official&nbsp;Hyv\u00e4&nbsp;documentation describes the theme as a Magento 2 frontend built with Tailwind CSS and Alpine.js instead of technologies such as Knockout,&nbsp;RequireJS, and LESS.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Because many Magento modules add layout XML intended for the traditional frontend,&nbsp;Hyv\u00e4&nbsp;needed a mechanism to reset or remove unnecessary blocks and layout instructions.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This was where the&nbsp;<strong>reset theme<\/strong>&nbsp;came into play.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Older&nbsp;Hyv\u00e4&nbsp;implementations could use:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&lt;<strong>parent<\/strong>&gt;Hyva\/reset&lt;\/<strong>parent<\/strong>&gt;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The reset theme&nbsp;contained&nbsp;layout reset instructions designed to remove or override Magento frontend elements that were not required by&nbsp;Hyv\u00e4.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For developers working on older&nbsp;Hyv\u00e4&nbsp;installations, this was an important part of the theme hierarchy.&nbsp;<\/p>\n\n\n<h2>What Changed in the Hyv\u00e4 Reset Architecture?<\/h2>\n\n\n<p class=\"wp-block-paragraph\">The important thing to understand is that Hyv\u00e4 did not simply \u201cdelete the reset theme.\u201d&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, Hyv\u00e4 changed&nbsp;<strong>how base layout resets are handled<\/strong>.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Starting with&nbsp;Hyv\u00e4&nbsp;Theme 1.3.18, the&nbsp;Hyv\u00e4&nbsp;Theme stopped using a reset-theme parent.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then, in&nbsp;Hyv\u00e4&nbsp;Theme 1.3.21,&nbsp;Hyv\u00e4&nbsp;introduced the:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">hyva-themes\/magento2-base-layout-reset&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">module.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">According to the official&nbsp;Hyv\u00e4&nbsp;documentation, the generated base layout reset was introduced to improve TTFB performance for cold-cache requests.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This&nbsp;represents&nbsp;an important architectural improvement.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\nThese architectural changes are also important when evaluating <a href=\"https:\/\/magecurious.com\/blog\/top-magento-2-hyva-compatible-extensions\">Magento 2 Hyv\u00e4-compatible extensions<\/a>, especially for extensions that add frontend functionality.\n<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of depending on&nbsp;a large collection&nbsp;of static&nbsp;layout&nbsp;reset XML files,&nbsp;Hyv\u00e4&nbsp;can generate the required base layout reset information.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Did Hyv\u00e4 Change the Hyv\u00e4 Reset Theme Architecture?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There are several reasons this approach is useful for modern Magento 2 stores.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Improved Cold-Cache Performance<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the main reasons for introducing generated base layout resets was improving&nbsp;<strong>Time to First Byte (TTFB)<\/strong>&nbsp;on cold-cache requests.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every&nbsp;layout&nbsp;XML file that Magento needs to process can contribute to the amount of work&nbsp;required&nbsp;during page generation.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By generating the relevant reset information,&nbsp;Hyv\u00e4&nbsp;can reduce unnecessary layout processing.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly important for Magento stores where performance is a major business requirement.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Less Manual Maintenance<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Traditional reset-theme implementations depended on predefined layout XML instructions.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As Magento introduced new modules and changed its frontend structure, reset definitions could require updates.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A generated approach makes it easier for the system to account for the current Magento installation.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This means developers&nbsp;don\u2019t&nbsp;have to think about&nbsp;maintaining&nbsp;a static reset list in the same way as before.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Better Compatibility&nbsp;With&nbsp;Magento Changes&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Magento continues to evolve.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">New Magento modules can introduce&nbsp;additional&nbsp;layout handles and&nbsp;frontend&nbsp;blocks.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A generated reset architecture can dynamically account for the modules present in the Magento installation rather than relying entirely on a fixed set of reset files.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This makes the approach more maintainable as Magento evolves.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Does the Hyv\u00e4 Reset Architecture Mean for Hyv\u00e4 1.4.0?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;1.4.0&nbsp;represents&nbsp;another major step forward for the&nbsp;Hyv\u00e4&nbsp;frontend.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The release modernizes the frontend with&nbsp;<strong>Tailwind CSS v4 and Design Tokens<\/strong>, while also introducing improvements such as enhanced HTML structures,&nbsp;BFCache&nbsp;support, Speculation Rules, and View Transitions.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;1.4.x uses Tailwind CSS v4, which changes configuration from the traditional JavaScript-based Tailwind configuration toward a CSS-first approach.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, developers upgrading an older&nbsp;Hyv\u00e4&nbsp;project to 1.4.x should not think about the reset-theme change in isolation.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A major&nbsp;Hyv\u00e4&nbsp;upgrade can involve several areas:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;Theme&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp; \u2193&nbsp;<br>Theme Module&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp; \u2193&nbsp;<br>Base Layout Reset&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp; \u2193&nbsp;<br>Tailwind CSS&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp; \u2193&nbsp;<br>Design Tokens&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp; \u2193&nbsp;<br>Custom Theme&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp; \u2193&nbsp;<br>Third-Party Extensions&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A proper upgrade should therefore include testing of the complete frontend architecture.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do Existing Projects Need to Migrate From the Reset Theme?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not necessarily.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is&nbsp;an important point&nbsp;for Magento developers.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">According to Hyv\u00e4\u2019s documentation, migrating an existing custom theme that directly extends&nbsp;Hyva\/reset&nbsp;is optional. Existing themes can continue using the reset theme.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So, if you have an older production Magento 2 store running successfully, you should not remove the reset theme blindly.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, first&nbsp;determine:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which&nbsp;Hyv\u00e4&nbsp;version you are running&nbsp;<\/li>\n\n\n\n<li>Which reset-theme package version is installed&nbsp;<\/li>\n\n\n\n<li>Whether your custom theme extends&nbsp;Hyva\/reset&nbsp;<\/li>\n\n\n\n<li>Whether any custom modules depend on the old architecture&nbsp;<\/li>\n\n\n\n<li>Whether third-party extensions detect&nbsp;Hyv\u00e4&nbsp;using the old theme hierarchy&nbsp;<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Then plan the migration.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Check Your Hyv\u00e4 Reset Theme Setup<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Start by checking your installed Composer packages.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">composer&nbsp;show hyva-themes\/magento2-default-theme&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can also check the reset-theme package:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">composer&nbsp;show&nbsp;hyva-themes\/magento2-reset-theme&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your project&nbsp;contains&nbsp;a custom theme, inspect:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">app\/design\/frontend\/Vendor\/Theme\/theme.xml&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Older themes may&nbsp;contain:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&lt;<strong>theme<\/strong>&nbsp;xmlns:xsi=&#8221;http:\/\/www.w3.org\/2001\/XMLSchema-instance&#8221;&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;xsi:noNamespaceSchemaLocation=&#8221;urn:magento:framework:Config\/etc\/theme.xsd&#8221;&gt;&nbsp;<br>&nbsp;<br>&nbsp;&nbsp;&nbsp; &lt;<strong>title<\/strong>&gt;Custom&nbsp;Hyv\u00e4&nbsp;Theme&lt;\/<strong>title<\/strong>&gt;&nbsp;<br>&nbsp;<br>&nbsp;&nbsp;&nbsp; &lt;<strong>parent<\/strong>&gt;Hyva\/reset&lt;\/<strong>parent<\/strong>&gt;&nbsp;<br>&nbsp;<br>&lt;\/<strong>theme<\/strong>&gt;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is something worth reviewing during an upgrade.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Migrating From the Legacy Hyv\u00e4 Reset Architecture<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;provides documentation for migrating custom base themes from the old reset-theme architecture to generated base layout resets.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The migration process depends on how your project is structured.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One important consideration is that&nbsp;Hyv\u00e4&nbsp;needs to know which themes should be treated as&nbsp;Hyv\u00e4&nbsp;base themes.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For custom base themes,&nbsp;Hyv\u00e4&nbsp;documents&nbsp;registering&nbsp;the theme through the&nbsp;Hyva\\Theme\\Service\\HyvaThemes&nbsp;configuration.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly relevant for agencies and Magento developers who&nbsp;maintain&nbsp;their own reusable&nbsp;Hyv\u00e4&nbsp;base themes.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Useful&nbsp;Hyv\u00e4&nbsp;Base Layout Reset Commands<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;provides commands that can help developers inspect and migrate base layout reset configurations.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">bin\/magento&nbsp;hyva:base-layout-resets:info&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The migration tooling can also be used for a custom theme:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">bin\/magento&nbsp;hyva:base-layout-resets:migrate&nbsp;Vendor\/theme&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Always review the generated changes before committing them to your production project.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The goal should not simply be to run a migration command and deploy&nbsp;immediately.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Backup&nbsp;<br>&nbsp; \u2193&nbsp;<br>Upgrade in development&nbsp;<br>&nbsp; \u2193&nbsp;<br>Run migration&nbsp;<br>&nbsp; \u2193&nbsp;<br>Review generated changes&nbsp;<br>&nbsp; \u2193&nbsp;<br>Test frontend&nbsp;<br>&nbsp; \u2193&nbsp;<br>Test checkout&nbsp;<br>&nbsp; \u2193&nbsp;<br>Test extensions&nbsp;<br>&nbsp; \u2193&nbsp;<br>Deploy&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why the Hyv\u00e4 Reset Architecture Matters to Magento 2 Extension Developers<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is where the change becomes especially interesting for&nbsp;<strong>Magento 2 extension vendors<\/strong>.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many Magento extensions need to&nbsp;determine&nbsp;whether the current storefront is running&nbsp;Hyv\u00e4.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Historically, developers sometimes checked the theme inheritance chain for:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyva\/reset&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, custom code may have assumed that a&nbsp;Hyv\u00e4&nbsp;theme always inherits from:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyva\/reset&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That assumption is no longer reliable for newer&nbsp;Hyv\u00e4&nbsp;implementations.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;provides theme detection functionality through its theme service architecture. The&nbsp;isHyvaTheme&nbsp;functionality is associated with the newer base layout reset architecture.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This means extension developers should avoid building&nbsp;Hyv\u00e4&nbsp;detection logic around a hard-coded assumption such as:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">$theme-&gt;getParentTheme()-&gt;getCode()&nbsp;===&nbsp;&#8216;Hyva\/reset&#8217;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, use the supported&nbsp;Hyv\u00e4&nbsp;theme detection mechanisms.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is an important consideration for any Magento 2 extension that provides:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hyv\u00e4&nbsp;templates&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hyv\u00e4-specific layout XML&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hyv\u00e4&nbsp;JavaScript&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hyv\u00e4&nbsp;CSS&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hyv\u00e4&nbsp;checkout integration&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hyv\u00e4&nbsp;compatibility modules&nbsp;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">What Should MageCurious Extension Developers Check?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">At&nbsp;MageCurious, we believe Hyv\u00e4 compatibility should be considered during extension architecture\u2014not added as an afterthought.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When developing or updating a Magento 2 extension for&nbsp;Hyv\u00e4, developers should review several areas.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Theme Detection&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Don\u2019t&nbsp;assume:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyva\/reset&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">will&nbsp;always be present.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use the supported&nbsp;Hyv\u00e4&nbsp;theme detection approach.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Layout XML<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review all layout XML files and&nbsp;identify&nbsp;whether they depend on Luma-specific structures.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Templates&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check whether&nbsp;.phtml&nbsp;templates&nbsp;contain&nbsp;assumptions about:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Knockout&nbsp;<\/li>\n\n\n\n<li>RequireJS&nbsp;<\/li>\n\n\n\n<li>UI Components&nbsp;<\/li>\n\n\n\n<li>Luma-specific CSS classes&nbsp;<\/li>\n\n\n\n<li>Magento JavaScript components&nbsp;<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">JavaScript&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Traditional Magento frontend JavaScript may not work correctly in a&nbsp;Hyv\u00e4&nbsp;storefront.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4 uses Alpine.js and a different frontend architecture.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">CSS&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4\u2019s Tailwind-based architecture requires a different approach to styling.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With&nbsp;Hyv\u00e4&nbsp;1.4.x, developers must also consider Tailwind CSS v4 changes.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Third-Party Integrations&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Payment gateways, shipping integrations, product customization tools, tracking modules, and other&nbsp;frontend-heavy extensions should be tested separately.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hyv\u00e4&nbsp;1.4.0 and Tailwind CSS v4: Another Important Upgrade Consideration&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The reset architecture&nbsp;isn\u2019t&nbsp;the only major change developers need to consider.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;1.4.0 uses Tailwind CSS v4.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tailwind v4 changes the configuration model significantly.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of relying primarily on:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">tailwind.config.js&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tailwind v4 uses a CSS-first configuration approach.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;also introduced Design Tokens to make theme customization easier and more consistent.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For existing&nbsp;Hyv\u00e4&nbsp;projects, this means a 1.4.x upgrade should include a review of:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">tailwind.config.js&nbsp;<br>CSS imports&nbsp;<br>Custom utilities&nbsp;<br>Theme colors&nbsp;<br>Spacing&nbsp;<br>Typography&nbsp;<br>Third-party module CSS&nbsp;<br>Custom components&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4&nbsp;provides upgrade helper tooling to&nbsp;assist&nbsp;with migrating Tailwind CSS v3 projects to v4.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hyv\u00e4&nbsp;Upgrade Checklist for Magento 2 Developers&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before upgrading an existing Magento 2 store to a newer&nbsp;Hyv\u00e4&nbsp;version, we recommend using the following checklist.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Theme&nbsp;<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Check the current&nbsp;Hyv\u00e4&nbsp;Theme version&nbsp;<\/li>\n\n\n\n<li>Check the&nbsp;Hyv\u00e4&nbsp;Theme Module version&nbsp;<\/li>\n\n\n\n<li>Check the current Magento version&nbsp;<\/li>\n\n\n\n<li>Review custom theme inheritance&nbsp;<\/li>\n\n\n\n<li>Check whether&nbsp;Hyva\/reset&nbsp;is being used&nbsp;<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Composer&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">composer&nbsp;show&nbsp;hyva-themes\/magento2-default-theme&nbsp;<br>composer&nbsp;show&nbsp;hyva-themes\/magento2-theme-module&nbsp;<br>composer&nbsp;show&nbsp;hyva-themes\/magento2-reset-theme&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Base Layout Reset<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">bin\/magento&nbsp;hyva:base-layout-resets:info&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If&nbsp;appropriate, evaluate:&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">bin\/magento&nbsp;hyva:base-layout-resets:migrate&nbsp;Vendor\/theme&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Frontend<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Test:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Homepage&nbsp;<\/li>\n\n\n\n<li>Category pages&nbsp;<\/li>\n\n\n\n<li>Product pages&nbsp;<\/li>\n\n\n\n<li>Search&nbsp;<\/li>\n\n\n\n<li>Cart&nbsp;<\/li>\n\n\n\n<li>Customer account&nbsp;<\/li>\n\n\n\n<li>Login&nbsp;<\/li>\n\n\n\n<li>Registration&nbsp;<\/li>\n\n\n\n<li>Checkout&nbsp;<\/li>\n\n\n\n<li>Forms&nbsp;<\/li>\n\n\n\n<li>Modals&nbsp;<\/li>\n\n\n\n<li>Navigation&nbsp;<\/li>\n\n\n\n<li>Mobile layouts&nbsp;<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Extensions&nbsp;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pay special attention to:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Payment methods&nbsp;<\/li>\n\n\n\n<li>Shipping modules&nbsp;<\/li>\n\n\n\n<li>Product options&nbsp;<\/li>\n\n\n\n<li>Wishlist&nbsp;<\/li>\n\n\n\n<li>Reviews&nbsp;<\/li>\n\n\n\n<li>Search&nbsp;<\/li>\n\n\n\n<li>Layered navigation&nbsp;<\/li>\n\n\n\n<li>Analytics&nbsp;<\/li>\n\n\n\n<li>Cookie\/consent modules&nbsp;<\/li>\n\n\n\n<li>Custom Magento extensions&nbsp;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Hyv\u00e4 Reset Architecture Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is the Hyv\u00e4 Reset Theme completely removed?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not exactly.<br>The more accurate description is that newer Hyv\u00e4 Theme versions no longer use the reset theme as the parent architecture. Hyv\u00e4 1.3.21 introduced generated base layout resets, while existing projects can continue using the old reset theme if required.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When did Hyv\u00e4 stop using the reset-theme parent?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Hyv\u00e4\u2019s upgrade documentation states that since release <strong>1.3.18<\/strong>, Hyv\u00e4 Theme no longer uses a reset-theme parent.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need to migrate my existing Hyv\u00e4 theme?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not necessarily. <br>Migration is optional for existing themes that directly extend <strong>Hyva\/reset<\/strong>. However, developers should evaluate the benefits of moving to the generated base layout reset architecture when planning a broader Hyv\u00e4 upgrade.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is magento2-base-layout-reset?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It is the Hyv\u00e4 module responsible for the newer generated base layout reset approach. It was introduced with Hyv\u00e4 Theme 1.3.21 and is designed to improve performance and simplify maintenance of layout reset information.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does this affect Magento 2 extensions?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes, potentially. <br>Extensions that detect Hyv\u00e4 by checking for <strong>Hyva\/reset<\/strong> or rely on the old theme inheritance structure should be reviewed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is this related to Tailwind CSS v4?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">They are separate changes, but both are important when upgrading to modern Hyv\u00e4 versions.<br>Hyv\u00e4 1.4.x uses Tailwind CSS v4 and introduces a more modern CSS architecture with Design Tokens.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Final Thoughts&nbsp;<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The evolution from the traditional Hyv\u00e4 reset architecture to generated base layout resets is more than a simple Composer package change.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It&nbsp;represents&nbsp;a broader effort to make&nbsp;Hyv\u00e4\u2019s&nbsp;Magento 2 frontend architecture:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Faster<\/li>\n\n\n\n<li>Easier to maintain<\/li>\n\n\n\n<li>More adaptable to Magento changes<\/li>\n\n\n\n<li>Less dependent on static layout reset definitions<\/li>\n\n\n\n<li>Better suited for modern Magento development<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For existing stores, there is no reason to panic or immediately remove the legacy reset theme or magento2-reset-theme package. The migration should be planned and tested based on the project\u2019s current Hyv\u00e4 version, theme architecture, and customizations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For new projects, however, developers should follow the current&nbsp;Hyv\u00e4&nbsp;architecture rather than copying patterns from older&nbsp;Hyv\u00e4&nbsp;implementations.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same principle applies to Magento 2 extension developers.&nbsp;<br>As&nbsp;Hyv\u00e4&nbsp;evolves, extensions should avoid relying on assumptions from older versions.&nbsp;Hyv\u00e4&nbsp;compatibility should be built around supported APIs, theme detection mechanisms, modern layout architecture, and the current frontend stack.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At\u00a0<strong><a href=\"https:\/\/magecurious.com\/hyva-magento2-development\">MageCurious<\/a><\/strong>, we focus on building Magento 2 solutions with modern frontend requirements in mind, including\u00a0Hyv\u00e4\u00a0compatibility. As a\u00a0<strong>Hyv\u00e4\u00a0Bronze Partner<\/strong>, we continue to follow the evolving\u00a0Hyv\u00e4\u00a0ecosystem and help Magento merchants and developers build faster, maintainable storefronts.\u00a0<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Working on a Magento 2 store migration to&nbsp;Hyv\u00e4&nbsp;or upgrading an existing&nbsp;Hyv\u00e4&nbsp;implementation?&nbsp;MageCurious&nbsp;can help you review your theme and extension compatibility and prepare your store for the latest&nbsp;Hyv\u00e4&nbsp;architecture.<\/strong>&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">References&nbsp;<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/docs.hyva.io\/hyva-themes\/upgrading\/index.html\">Hyv\u00e4 Theme Upgrade Documentation<\/a><\/li>\n\n\n\n<li>Hyv\u00e4 Generated Base Layout Resets Documentation<\/li>\n\n\n\n<li>Hyv\u00e4 1.3.21 Upgrade Documentation<\/li>\n\n\n\n<li>Hyv\u00e4 1.4.0 Upgrade Documentation<\/li>\n\n\n\n<li><a href=\"https:\/\/docs.hyva.io\/hyva-themes\/working-with-tailwindcss\/updating-to-tailwind-4.html\">Hyv\u00e4 Tailwind CSS v4 Documentation<\/a><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction The traditional Hyv\u00e4 reset architecture has been an important part of Magento 2 frontend development for older Hyv\u00e4 projects. As Hyv\u00e4 has evolved, the way Magento layout resets are handled has changed significantly. Newer Hyv\u00e4 Theme versions no longer use the traditional reset-theme parent, introducing a more modern generated base layout reset architecture. As [&hellip;]<\/p>\n","protected":false},"author":9,"featured_media":2175,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[154,4],"tags":[],"class_list":["post-2174","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hyva","category-magento-2"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Hyv\u00e4 Reset Theme: What Magento 2 Developers Need to Know<\/title>\n<meta name=\"description\" content=\"Learn what changed with the Hyv\u00e4 Reset Theme, why Hyva\/reset is no longer the parent theme, and how Magento 2 developers can migrate.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Hyv\u00e4 Reset Theme: What Magento 2 Developers Need to Know\" \/>\n<meta property=\"og:description\" content=\"Learn what changed with the Hyv\u00e4 Reset Theme, why Hyva\/reset is no longer the parent theme, and how Magento 2 developers can migrate.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/\" \/>\n<meta property=\"og:site_name\" content=\"Magecurious\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-02T08:44:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-07T11:26:34+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/09\/hyva-theme-remove-the-reset-theme.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"496\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Shradhdha Prajapati\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Shradhdha Prajapati\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Hyv\u00e4 Reset Theme: What Magento 2 Developers Need to Know","description":"Learn what changed with the Hyv\u00e4 Reset Theme, why Hyva\/reset is no longer the parent theme, and how Magento 2 developers can migrate.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/","og_locale":"en_US","og_type":"article","og_title":"Hyv\u00e4 Reset Theme: What Magento 2 Developers Need to Know","og_description":"Learn what changed with the Hyv\u00e4 Reset Theme, why Hyva\/reset is no longer the parent theme, and how Magento 2 developers can migrate.","og_url":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/","og_site_name":"Magecurious","article_published_time":"2026-09-02T08:44:40+00:00","article_modified_time":"2026-09-07T11:26:34+00:00","og_image":[{"width":1200,"height":496,"url":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/09\/hyva-theme-remove-the-reset-theme.png","type":"image\/png"}],"author":"Shradhdha Prajapati","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Shradhdha Prajapati","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#article","isPartOf":{"@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/"},"author":{"name":"Shradhdha Prajapati","@id":"https:\/\/magecurious.com\/blog\/#\/schema\/person\/e96648a34af2c987eec973e2aa210be9"},"headline":"Hyv\u00e4 Theme Removes the Reset Theme: What Magento 2 Developers Need to Know\u00a0","datePublished":"2026-09-02T08:44:40+00:00","dateModified":"2026-09-07T11:26:34+00:00","mainEntityOfPage":{"@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/"},"wordCount":2688,"commentCount":0,"publisher":{"@id":"https:\/\/magecurious.com\/blog\/#organization"},"image":{"@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#primaryimage"},"thumbnailUrl":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/09\/hyva-theme-remove-the-reset-theme.png","articleSection":["Hyva","Magento 2 Blog"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/","url":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/","name":"Hyv\u00e4 Reset Theme: What Magento 2 Developers Need to Know","isPartOf":{"@id":"https:\/\/magecurious.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#primaryimage"},"image":{"@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#primaryimage"},"thumbnailUrl":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/09\/hyva-theme-remove-the-reset-theme.png","datePublished":"2026-09-02T08:44:40+00:00","dateModified":"2026-09-07T11:26:34+00:00","description":"Learn what changed with the Hyv\u00e4 Reset Theme, why Hyva\/reset is no longer the parent theme, and how Magento 2 developers can migrate.","breadcrumb":{"@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#primaryimage","url":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/09\/hyva-theme-remove-the-reset-theme.png","contentUrl":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/09\/hyva-theme-remove-the-reset-theme.png","width":1200,"height":496,"caption":"Hyv\u00e4 Reset Theme and generated base layout reset architecture"},{"@type":"BreadcrumbList","@id":"https:\/\/magecurious.com\/blog\/hyva-theme-removes-the-reset-theme-what-magento-2-developers-need-to-know\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/magecurious.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Hyv\u00e4 Theme Removes the Reset Theme: What Magento 2 Developers Need to Know\u00a0"}]},{"@type":"WebSite","@id":"https:\/\/magecurious.com\/blog\/#website","url":"https:\/\/magecurious.com\/blog\/","name":"Magecurious","description":"Blog","publisher":{"@id":"https:\/\/magecurious.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/magecurious.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/magecurious.com\/blog\/#organization","name":"Magecurious","url":"https:\/\/magecurious.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/magecurious.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/03\/cropped-New_Project.png","contentUrl":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/03\/cropped-New_Project.png","width":596,"height":113,"caption":"Magecurious"},"image":{"@id":"https:\/\/magecurious.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/magecurious.com\/blog\/#\/schema\/person\/e96648a34af2c987eec973e2aa210be9","name":"Shradhdha Prajapati","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/magecurious.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/9d1c9c29f1ddbbd37b33de03b0685bfac9661d8ddcc664255eb317605ddc646c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9d1c9c29f1ddbbd37b33de03b0685bfac9661d8ddcc664255eb317605ddc646c?s=96&d=mm&r=g","caption":"Shradhdha Prajapati"},"url":"https:\/\/magecurious.com\/blog\/author\/shradhdha-magecurious\/"}]}},"jetpack_featured_media_url":"https:\/\/magecurious.com\/blog\/wp-content\/uploads\/2026\/09\/hyva-theme-remove-the-reset-theme.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/posts\/2174","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/comments?post=2174"}],"version-history":[{"count":6,"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/posts\/2174\/revisions"}],"predecessor-version":[{"id":2186,"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/posts\/2174\/revisions\/2186"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/media\/2175"}],"wp:attachment":[{"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/media?parent=2174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/categories?post=2174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/magecurious.com\/blog\/wp-json\/wp\/v2\/tags?post=2174"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}