https://embed.notionlytics.com/wt/ZXlKd1lXZGxTV1FpT2lJeE16WmlNREpsWVdOaU16WTBaakV4T1dOaU5tSTBOekUyTlRrMU5UZzVOU0lzSW5kdmNtdHpjR0ZqWlZSeVlXTnJaWEpKWkNJNklrbGpiM1pzV2pOcU1VUnBRM1ZUUm1WNFRtdHlJbjA9

Every project is a code (one line, two, one hundred, and so on). It is easy to get confused in a project with no code structure. But there is a solution – modules.

What is a module?

A module is a part of the code that is responsible for certain functionality.

Modules help us or our team write code with small parts that can be connected or can be used by another small part of the code. This approach is such a good thing to get a consistent, clear, and debuggable structure for the project.

Questions to answer

• What will my module do?
• How to name my module?
• Which modules must be loaded before my module can start working?
• What Magento 2 entities do I plan to interact this module?
• Do I want to share this module?

How should a module be named?

The name of the module must consist of two parts: vendor name and module name:

• vendor name – If you develop a basic module that is not going to be shared across other projects, then the vendor name is the same as the project name.** In case you develop a module that will be shared across projects or teams you should specify Scandiweb as a vendor of a module. It is a good practice to add the composer.json file to a shared module.
• module name – how the module is called. The name of the module should be informative and should reflect the task that it solves.

Where should a module be located?

When developing a module we should put its source according to the conventional folder structure:

/app/code/<VENDOR_NAME>/<MODULE_NAME>/