Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Mastering Adobe Commerce Frontend

You're reading from  Mastering Adobe Commerce Frontend

Product type Book
Published in Mar 2024
Publisher Packt
ISBN-13 9781837637072
Pages 402 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Jakub Winkler Jakub Winkler
Profile icon Jakub Winkler

Table of Contents (18) Chapters

Preface 1. Chapter 1: Setting Up the Local Environment 2. Chapter 2: Installing the Magento/Adobe Commerce Application 3. Chapter 3: Introduction to Adobe Commerce Theming 4. Chapter 4: The Layout System 5. Chapter 5: Working with Templates 6. Chapter 6: Styling an Adobe Commerce Theme 7. Chapter 7: Customizing Emails 8. Chapter 8: Introduction to JavaScript Libraries and Frameworks 9. Chapter 9: RequireJS and jQuery 10. Chapter 10: Knockout.js and UI Components 11. Chapter 11: Commonly Used Libraries Bundled with Adobe Commerce 12. Chapter 12: Storefront-Related Configuration in the Admin Panel 13. Chapter 13: Working with Magento CMS 14. Chapter 14: Frontend Optimization Techniques 15. Chapter 15: Common Tools that Help with Local Development 16. Index 17. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}