Magento Model vs Block vs Controller etc

Magento Model vs Block vs Controller etc

July 18, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento Model vs Block vs Controller etc

Understanding Magento Module Subfolders: A Comprehensive Guide

Welcome developers! Today, we’re going to demystify one of Magento’s core architectural components - the module subfolders. As seasoned PHP developers at LaravelCompany, we’ve encountered many questions about these folders and their purpose. Let’s dive in!

Magento Modules Explained

Before we delve into the subfolders, let’s quickly recap what a Magento module is. A module is essentially a namespace that contains all the necessary code for a specific feature or functionality within your Magento application.

Each module has its own folder structure under app/code, and it follows a naming convention of CompanyName_ModuleName.

The Six Essential Subfolders

Let’s explore each subfolder in detail:

1. Controller

The controllers folder contains the controller classes that handle HTTP requests and responses for your module. Controllers are responsible for routing data between models, views, and the user.

For example, a typical controller might look like this:

namespace CompanyName\ModuleName\Controller;

class Index extends \Magento\Framework\App\Action\Action
{
    public function execute()
    {
        // Your logic here
    }
}

2. Model

The models folder houses the business logic and data access layers of your module. These classes interact with your database via Magento’s ORM.

Here’s a simple model:

namespace CompanyName\ModuleName\Model;

class MyModel extends \Magento\Framework\Model\AbstractModel
{
    protected function _construct()
    {
        $this->_init('CompanyName\ModuleName\Model\ResourceModel\MyModel');
    }
}

3. Block

The blocks folder contains the view layer components that render your module’s data on the frontend or admin panel.

A block might look like this:

namespace CompanyName\ModuleName\Block;

class MyBlock extends \Magento\Framework\View\Element\Template
{
    public function __construct(\Magento\Framework\View\Element\Context $context)
    {
        parent::__construct($context);
    }
}

4. Helper

The helpers folder houses utility classes that provide additional functionality, like configuration retrieval or data manipulation.

A helper might look like this:

namespace CompanyName\ModuleName\Helper;

class Data extends \Magento\Framework\App\Helper\AbstractHelper
{
    const XML_PATH_SAMPLE = 'sample/path/to/config';
}

5. Config

The config.xml file in the module’s root folder defines the module’s configuration, including its dependencies on other modules.

6. etc

This folder contains additional configuration files like module definitions (module.xml), layout XML files for the frontend or admin panel, and theme configuration files.

Conclusion: The Importance of Understanding Subfolders

Understanding Magento’s module subfolder structure is a crucial part of being an effective Magento developer. This knowledge enables you to create clean, maintainable code that adheres to Magento’s best practices.

Remember, each subfolder has a specific purpose in the MVC (Model-View-Controller) architecture that Magento follows. Models handle data operations, controllers manage routing and request/response cycles, blocks render views, and so on.

If you’re looking for more in-depth guidance on Magento development, be sure to check out our comprehensive guides at LaravelCompany. We cover everything from setup to advanced customization techniques.

Happy coding!

Indexing Database Extensions

Our network