The brixy/Modules folder contains all default modules that can be used in Brixy App Builder.

The brixy/Extensions/Modules folder contains all additional modules that can be used to extend Brixy App Builder.

Each folder contains the directories and files of one module. Each module can be used EITHER in the development environment OR in a application environment based on section value.

Having a module in the modules folder does not mean that it can be used directly in any template or layout file. For this to be possible, it must be added and configured via https://YOURDOMAIN.COM/brixyadmin/modules.
It can then be loaded via:
- module_id

$dt = [
	'loadmoduleid' => 2,
];
load_module($dt);
OR
load_module(['loadmoduleid' => 2]);

- position

load_modules_position('contact_form');

Each module folder can contain a json file with the following sample content:   

{
    "name":"mod_brixy_shop_shipping_speedy",
    "section":"app",
    "category":"module_category",
    "group":"brixy_shop_shipping",
    "version":"1"
}

When a group is set for module, if necessary, a link to menu can be created to load in your application a list containing all modules from a selected group. In order to display a given module in this list, it must have a json file in which the name of the selected group of modules is recorded. So modules can be edited outside the development environment, ie. as part of an application. For each module, its name and its published status are displayed.

The mod_menu_vertical_system folder contains the files for a module that displays the Brixy system menu. This module exists in the database, but does not appear in the list of modules with settings editable. Its settings cannot be changed. It is always displayed in the development environment ie. it will only be visible to users who have dev or superuser rights.

The mod_menu_vertical_dev folder contains the files for a module that displays the data of a selected created menu. It is only loaded in the development environment ie. it will only be visible to users who have dev or superuser rights and the user right set in the module settings matches the right of the logged in user. If the module is set to be visible ONLY to users with superuser rights, then users who do not have this right will not see the menu, but can open links from it if they have rights to do so.