Basic Concepts

Public and Private Interfaces

Originally, the system was designed to have three interfaces.
The public one, which was the usual www, or the website's main page; a private one for the user, which was designed to allow them access to documents or data generated; and a private one for system administrators, where they could have access to system control.
Each of these were on different subdomains.

Practice led to the realization that in the case of the user interface, this was not always necessary, as it could be an informational site without user accounts; In addition, it made administration more complicated.

Currently, the public and private user interfaces have been merged, although with minor modifications, they could be separated again so that the user doesn't have to leave the main interface.
For administrators, they continue to be managed separately for privacy reasons.

Modules as Service and Subservice Catalogs

The system is based on data catalogs (tables) that interact with each other according to the purpose and nature of the data being managed.
The main catalog is identified as a service, while those that interact under or above it are called subservice.

The modules are the grouping of a service, its related subservices, and the routines, applications, libraries, and various resources necessary for them to interact with each other.

Scripts and Data Processing

Each service and subservice is assigned a script that processes the information received. This script can be programmed in the language of choice and executed as a script or CGI. Historically, CGIs began using Perl, but the decision was made to open source this to the programmer's choice; this is because different sites may require different types of internal data processing, so the programmer must be able to implement these processes in the language that best suits their needs.