In Tribiq CMS, Modules represent units of functionality. Modules can be simple or complex. Some Modules create Plugins that can be inserted in a Slot on a page.

When a Module is installed and run, it can create and populate its own database tables. A Module can add its own database management to the Admin Back-end. Such functionality is defined in TUIX - Tribiq User Interface XML.

One Module can replace another Module by extending the first Module's functionality. This enables effective reuse of the Module's code. In this example "A" adds to the functionality of "B".

A Module can expose public static methods to other Modules, so that those Modules may use its functionality. This forms part of a Module's API. In the example below, Module A is calling static methods of Module C

A Module can send a Signal when some event occurs. This Signal can received by other Modules. Signals are also sent by the Core following certain actions, for example, the Core sends a Signal when a Content Item is Published so that other Modules may act on this event.

A Module can create Plugins to display output on the website's front-end. The HTML structure is defined by a Framework. The styling is defined by the Skin of the Page, or the Plugin's Swatch. Some Plugins can also use Visitor Phrases for multi-language support.

Using a combination of the techniques below opens up powerful possibilities for creating complete solutions.  For example, you can build a data management tool in Storekeeper (the backend) and then display the data in the frontend to your visitors.