Book Image

Mastering Adobe Commerce Frontend

By : Jakub Winkler
Book Image

Mastering Adobe Commerce Frontend

By: Jakub Winkler

Overview of this book

Navigating the frontend realm of the Adobe Commerce platform can often feel like a labyrinth, given its multifaceted systems and intricate layering. This book demystifies Adobe Commerce frontend development, guiding you through its paths with clarity and precision. You'll learn how to set up your local environment, paving the way for a smooth development experience and navigate the platform's theming ecosystem, exploring layout XML systems and the power of templates. As you progress through the book, you'll leverage an array of JavaScript libraries and frameworks that Adobe Commerce boasts of, with special emphasis on RequireJS, jQuery, Knockout.JS, and UI Components. Additionally, you'll gain an understanding of the intricacies of Adobe Commerce CMS, explore frontend-related configurations in the admin panel, and unlock the secrets of frontend optimization. Practical exercises provided in the book will enable you to create top-notch Adobe Commerce sites that are functional, optimized, user-centric, and a step ahead in the ever-evolving frontend landscape.
Table of Contents (18 chapters)

Caching system

Take a look in the vendor/magento folder in your IDE and open any module; let’s use magento-catalog as an example.

Please open the etc folder, and you will see a lot of XML files (along with other files). Those XML files represent the configuration of the module and are responsible for a lot of system-wide-related events and platform customization.

You can say that XML files are the heart of Magento/Adobe Commerce configuration.

Figure 3.6 – Magento 2 XML files from the catalog module

Figure 3.6 – Magento 2 XML files from the catalog module

Don’t worry; we won’t be discussing every single file located in that folder; the purpose of this is to show you that Magento 2 has a lot of configuration files to process when the framework is initialized. Those configuration files are defined for each module, and there are thousands of them in the framework itself. If Magento were to read all of them every single time an application is initialized, it would take at least...