Book Image

Magento 2 Theme Design - Second Edition

By : Richard Carter
Book Image

Magento 2 Theme Design - Second Edition

By: Richard Carter

Overview of this book

Magento is the e-commerce software and platform trusted by the world’s leading brands. Using Magento’s powerful theming engine, you can control the look, content, and functionality, and easily launch a flexible e-commerce website. However, because of its powerful features, developing Magento themes is easier said than done. This book aims to leverage the enhancements to theme designing in Magento 2 to the fullest. It will show you how to gear up the performance of your e-commerce website. We begin by introducing Magento 2 and its features along with implementing a local development Magento environment. We then move on to discuss the concepts of the Magento theme structure such as templates, inheritance, customization, and override. Further on, we explore the Magento UI Library, which is a new feature available in Magento 2.0. We will create a new Magento 2.0 theme named MyCake Store using Magento Bootstrap from Maven E-commerce and also create print strategies for the Magento 2.0 theme. We will also create and customize a new theme proposal for the Magento admin panel. At the end, we will integrate Magento 2.0 to Twitter and integrate it with social bookmarking and finally deploy our new Magento 2.0 theme.
Table of Contents (18 chapters)
Magento 2 Theme Design - Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

UI components control definition file


All of these items listed as UI components are managed by the UI module. The UI Module centralizes the statements in the file <magento_root>/vendor/magento/module-ui/view/base/ui_component/etc/definiton.xml, which are available with all UI components, represented by the following code segment:

The UI module searches in all modules to see if there is a new statement or a call for the UI components on the ui_component directory, as previously seen. This same rule applies to the definition.xml configuration file, in case you want to have a specific configuration in your module.

This case is applicable only if you want to customize the UI components functionalities in a global way. For adjustments and punctual statements it is recommended to follow the notation demonstrated in this chapter through the following application examples:

<module_root>/<vendor>/<module>/view/<area>/ui_component/<component_instance_name>.xml...