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)

Layout overrides

We’ve been over page layouts, page configurations (handles), and layout instructions (blocks, containers, and so on) and how they are processed to render a page. It might seem a little “limited” that this process is always done via “XML merging” and then the rendering process. AC core developers call this process “layout extending” in the official documentation and it might seem a little limited.

Preparing a customized wireframe might seem like a huge challenge. Moving and setting up containers and blocks, as well as removing unwanted elements from certain pages or all pages, seems like a lot of time that should be saved as customizations should be done much easier, right?

AC core developers are aware of this and that is why they created a way to override (or simply tell the code to skip some steps) the core layout files and limit the XML merging process only to the bare minimum. This is the way highly customized...