Modularity, multilingual support, portability

Several content management systems (CMS) use a multi-tiered structure, in which data is retrieved from the database and displayed on screen as it is retrieved, often including a predefined style. In more robust systems, this has been eliminated, but the code or visual representation now becomes the challenge, which in some cases means that special changes and modifications require an additional investment of time and effort.

The goal of the system is to be organized in a modular manner, where each layer is fully identifiable in terms of location, function, and requirements. It must provide complete and reliable information to the upper modules, so that they can be transformed without the need for cross-validation.

This type of structure allows elements to be exchanged without having to change the entire system. Thus, if you want to use a database other than MySQL, such as MariaDB, simply replace the database modules (obj_db) with the corresponding one. If instead of using jQuery as the JavaScript framework, you prefer AngularJS, Dojo, GWT, or MooTools, just specify it in the system configuration (admin panel > config).
In the case of responsive design, something similar happens. Perhaps you don't feel comfortable with the current system I created because you have more experience with others, you can change the configuration (admin panel > config) and replace the CSS loading with Bootstrap, Foundation, or something else; the same goes for scripts; you can replace the current Perl files with Ruby, Java, or Python.

In addition to these modular features, the system was also designed from the beginning to support Unicode, while also focusing (because worrying is pointless) on design elements to make the resulting appearance equally pleasing for both the user and what happens behind the scenes.

Other Features

In addition to the above, I've added small routines for data debugging that allow for quick problem detection and corrections without having to search for needles in a haystack, as well as security features in both programming and database design, parameters, and other elements.

In parameter passing, control characters are removed from user requests (except when sending data to a script) to prevent XSS attacks. Separate control panels have been created for users and administrators, along with descriptions of actions and validation for each of the services.
Regarding files and source code, a nomenclature based on Hungarian notation and a file structure that is as clear, concise, and portable as possible have been followed. as well as variables that allow you to perform real-time debugging actions.

I invite you to learn a little more about the system on these pages or in the corresponding documentation, or, if you wish, the story behind it.