![\"mod](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2015\/05\/mod_str11.png\" "\\"Magento")
<\/p>\nIn order to understand how a module works we need to find out how basic components like controller, model, block and view interact with each other. If you have already worked with Magento before you should know why we need these structural units and how the module structure was organized in previous Magento versions.<\/p>\n
It all looked like this:<\/p>\n
<\/p>\n
As we can see from this picture the module code was scattered across different directories (code, design, skin, etc).<\/p>\n
A module in Magento 2 is located in a single directory which simplifies the search and analysis of the extension’s logic. Now the standard module structure looks like this:<\/p>\n
![\"mod](\"https:\/\/belvg.com\/blog\/wp-content\/uploads\/2015\/05\/mod_str2.png\" "\\"Magento")
<\/p>\n
Let’s describe this structure. Once again all extensions are located in the app \/ code \/. Then the following logic works:<\/p>\n
The module includes the following:<\/p>\n
Understanding the module structure in Magento 2 allows analysis of the extension’s logic and performance as well as an easier job finding and fixing arising errors and conflicts.<\/p>\n\n","protected":false},"excerpt":{"rendered":"In order to understand how a module works we need to find out how basic …","protected":false},"author":42,"featured_media":10049,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"image","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,389],"tags":[3,382,64,83],"class_list":["post-7661","post","type-post","status-publish","format-image","has-post-thumbnail","hentry","category-magento","category-magento2-development","tag-magento","tag-magento-2-0","tag-module","tag-module-structure","post_format-post-format-image"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t