1-Navigate to your public_html

2-Now make any directory in it

3-Then run command in directory composer create-project --repository=https://repo.magento.com/ magento/project-community-edition .
Creating a "magento/project-community-edition" project at "./"

4-composer config repositories.private-packagist composer https://hyva-themes.repo.packagist.com/xyz-com/

Now it will ask for you two thing. One is Magento 2 marketplace keys that you can find from magento marketplace website free.

For hyva theme you need to buy licence and then will get token that you can use while installing hyva like in above command.

Now this is time to installl hyva them and we have already get repository auth so we are able to install theme now

5-composer require hyva-themes/magento2-default-theme

What Is hyva-themes.json?

You will find this file under app/etc and this file is a Hyvä compatibility mapping file used to register Hyvä-compatible module sources—specifically for the Hyvä Checkout and Admin modules.

This files looks like

{
    "extensions": [
        {
            "src": "vendor\/hyva-themes\/magento2-theme-module\/src"
        }
    ]
}

What It Does:

This file tells Hyvä to:

• Look into the listed src directories for Hyvä-compatible modules or UI components.

• Register and include them when generating view models, templates, or layout updates.

When you run Hyvä commands like:

The Magento community has been buzzing about Magento 3 for years. While Adobe hasn’t confirmed its development, industry trends suggest that if a next-gen Magento emerges, it’ll likely be:

Check Tag Manager Connection from this URL

https://tagassistant.google.com/?hl=en&utm_source=gtm#/?source=TAG_MANAGER&id=GTM-KG67ZJ95&gtm_auth=8xSYhrq97Wf1D0GG25DDHA&gtm_preview=env-3&cb=4450675755277849

https://www.pixelcut.ai/projects/280c19e4-7759-4aa6-8633-6c40af6ccc73/editor/

Create AI Videos

https://app.videogen.io/project/288d9bd8-4dda-4848-97c7-e7d28b7f2095?internalReferrerPath=%2F&_gl=1*kssssp*_gcl_aw*R0NMLjE3NDMwMDMyMzQuQ2owS0NRand5NDZfQmhET0FSSXNBSXZtY3dONE9TZ3pTMVM3WHAwd3lwRk1vRDZhSGJvTjdnR0hMVS1zVkthb0ZuY3luNGo0U0xDeGlFQWFBc01oRUFMd193Y0I.*_gcl_au*MjA4MzU0NjE2NS4xNzQzMDAzMjM0*_ga*MTU2Mjg3MjMwOC4xNzQzMDAzMjM0*_ga_8X6RQ6WMFR*MTc0MzAwMzIzMy4xLjEuMTc0MzAwMzIzMy42MC4wLjI1MDg1MTQ0Mw..*_ga_LH6ELLTQ11*MTc0MzAwMzIzMy4xLjEuMTc0MzAwMzIzMy42MC4wLjIwNDM4MTA1OQ..

Download after effects free

https://aepreset.com/

To add a new button, text in minicart. Add a node extra_info 

See how to add button text in minicart video

Get custom attribute in Magento 2 Minicart

https://www.magevision.com/blog/post/get-a-product-attribute-in-mini-cart-magento-2

https://shaneblandford.medium.com/magento-2-add-attributes-to-mini-cart-list-d583895a19db

Github module for Minicart

https://github.com/vijayrami/Magelearn_AdvanceCart

Magento 2's minicart can be customized to include several additional components or content items, each serving different purposes. Here are some commonly used components or areas you can add to the minicart:

1. Mini Cart Summary:

   • Component: Magento_Checkout/js/view/minicart/subtotal/totals
   • Purpose: Displays the subtotal, total discounts, taxes, or shipping costs.
   • Example Template: Magento_Checkout/minicart/summary

2. Custom Promotions Banner:

   • Component: Custom JavaScript component, e.g., Vendor_Module/js/view/promotions-banner
   • Purpose: Display promotional messages, discounts, or offers

You can stop checkout success page redirection after refresh page, check below code

vendor/magento/module-checkout/Controller/Onepage/Success.php

Comment Out Line No : 26 (in Magento 2.4)

//$session->clearQuote();

Areas and application entry points

Each module can have a global and area-specific di.xml file. The application reads all the di.xml configuration files declared in the system and merges them all together by appending all nodes.

As a general rule, the area specific di.xml files should configure dependencies for the presentation layer, and your module's global di.xml file should configure the remaining dependencies.

The application loads the configuration in the following stages:

1. Initial (app/etc/di.xml)
2. Global (<moduleDir>/etc/di.xml)
3. Area-specific (<moduleDir>/etc/<area>/di.xml)

The areas are:

• adminhtml
• frontend
• graphql
• webapi_rest
• webapi_soap
• crontab

During bootstrapping, each application entry point loads the appropriate di.xml files for the requested area.

Constructor arguments