Responsive web Framework


Multiple Layer Structure

System organized in a modular way, where each layer delivers validated and standardized information to the superiors, allowing a fast maintenance.


(minimum width: 480px)

Modularity, multilingual support, portability

Several of the content management systems (CMS) use a structure of a few layers, in which the data are taken from the database and as they are retrieved are displayed on the screen, often including a predefined style. On more robust systems, this has been eliminated, but the code or visual representation now becomes the challenge, which in some cases makes the changes and special modifications result in an investment of time and additional effort.

multilayer structure The objective of the system is to be organized in a modular way, where each layer is totally identifiable in terms of location, function and requirements, which must deliver complete and reliable information to the higher modules, so that they can be transformed for these without having to cross-validate.

This type of structure allows to exchange elements without requiring to change the whole system. Thus, if you want to use a database other than MySql to MariaDB simply replace the database modules (obj_db) with the corresponding one; If instead of using jQuery with another framework as AngularJS, Dojo, GWT o MooTools just modify it in the configuration (admin panel > config).
In the case of responsive design something similar happens, maybe you do not feel comfortable with the current system that I realized because you have a greater experience in others, you can change the configuration (admin panel > config) and change the CSS loading with Bootstrap, Foundation or some other; The same thing happens with the scripts, you can replace the current files made in Perl with Ruby, Java or Phyton.

To these modular features is added that the system was also thought from its beginnings to support Unicode at the same time to be concerned (because worry is useless) in design elements to make it equally pleasing in appearance resulting from what the user sees, as well as what happens behind the code.

Other features

In addition to the above, I have added small routines for debugging data that allow you to detect problems and make quick corrections without needing to search for needles in the haystack, as well as security elements in both programming and database design, parameters and other elements.

In parameter sending is the removal of control characters in user requests (except in sending data to script) in order to avoid XSS attacks, the creation of control panels for user and administrator, which is combined with the description of actions and validation for each of the services .
In terms of files and source code, a nomenclature based on Hungarian notation and a file structure have been followed as clear, short and portable possible; As well as variables that allow real-time debugging actions.

I invite you to know a little more about the system in these pages or in the documentation or visiting the history page about the system.