It is the smallest component of the builder. Modules are "bricks" for creating and formatting the page content or layout of the page. Each module has settings that are aimed to customise it.
Many modules have their unique settings and presets, which are located under the
Primary tab. Examples are a setting for content for the Paragraph module or a setting for a date for the Time module.
CSS settings are standard for all modules; they are located under the
Advanced tab. Under this tab also are settings for
class attributes and for any other custom or standard HTML attributes.
Opening module's settings makes such module an active one. For instance, some hotkeys work for active module only.
When several modules are "grouped" together, they form a layout. There is always one (and only one) parent module in the layout. So, every layout is a set (so-called "group") of several modules nested under one single parent.
These are built-in items or are added by third-party extensions via hooks.
These are copies of modules/layouts with specific settings which are saved to DB to be re-used in the same template or used in other templates. It is convenient to create a collection of design elements and have easy access to this collection from any template.
Saved modules are not available in the free version.
These are copies of modules/layouts with specific settings which are reusable across templates. Any changes in one instance of the global module will trigger updating all the same global module instances in all other templates.
Global modules are not available in the free version.
A template is a set or collection of modules combined in a specific way. It represents the layout of a particular page. In terms of entity, this is a particular JSON configuration.
When loaded the page in the builder mode, you should see a small logo icon on the screen's left (or right) edge. This icon opens the builder panel (Panel), where you can get access to all the builder settings, the possibility to add new modules, drag'n'drop them, save changes etc.
In terms of entity, builder content is a JSON configuration that describes a template.
In terms of place, this is the area where all added modules can be seen as HTML rendered on the page.
When we assign a template to specific WP objects, e.g. posts and pages, the latter become applicants. Each such WP object has its own data, e.g. posts have title, content, author ID etc, so WP object data become applicant data and is available in the builder through "data variables" (specifically, data variables with type "Query to DB")
Data variables are synthetic variables added by the user in the builder. They can hold some data or be empty.
A set of settings which are available for specific template only.
A set of settings which are available for all templates. However, these settings are also separated by template type, i.e, settings added for "single" type are not accessible for templates of type "collection". Global settings also can be assigned to all templates.
A set of settings that are available for the modules. Some module settings are the same across all modules, but others are specific to a particular module type.