History

The original idea of ​​creating a CMS came from working with several of them, which had emerged from a collaborative effort.

While they were easy to install and program, and offered countless features and utilities, due to the very fact that they were collaborative, they didn't follow a defined standard; instead, each programmer established their own criteria.

Another point I didn't like was that the data was presented exactly as it came from the database, combining information retrieval with its presentation. This made the design rigid, and modifying the functionality was quite a laborious task.

Almost all the systems I knew were based on a single language (PHP or ASP) to perform all their tasks, both querying and transforming data. Therefore, in the case of systems that required special processing, it was necessary to acquire external libraries, which were not always free. or the scope of development was limited. Given my knowledge of Perl and its repository of features, even though it was a language that was already years old, it seemed like a good option to leave everything related to data manipulation and conversion to this language, and data retrieval and presentation to the aforementioned.

Knowing that there is a wide variety of databases, that other programmers might want to use other languages ​​for their processes with which they would feel more comfortable, and the problems mentioned in my first paragraph, I opted to make it as modular as possible.

This first development was done in a structured way for Web 1.0-based systems. Over time, this evolved, the Web 2.0 trend came, and a friend made me see the need to reprogram this as objects. Unfortunately, many things got in the way, and I didn't do it, except for positioning it as a system that I would incorporate into my developments and sell it independently.

Over time, new tools and new features (like jQuery) appeared. I learned from previous implementations that some things were necessary and others weren't (I released about 7 versions before), and recently, with the responsive code, I had to add new utilities.

This is what led me to release this new version, which, due to the modifications it has undergone over time, its reprogramming, and the incorporation of technologies, I chose to call version 10, although it may only be version 6 or 7.

It's true that I still have a lot of progress and reorganization to make from the current version, and that new changes will occur as it is tested, reviewed, and all that. But as I move forward (or as we move forward on that path), here it is available, hoping it will be useful.

Versions

The name SiteUP! has changed over time. At first, it didn't have a defined name because it was just a set of features, which were grouped together as they grew under the name JPanel.

As time went by and elements were added, I decided to make it a little more formal. I replaced the name with something that began with e-, but since that was already very outdated, I opted to use i- and leave it as i-Mentha, which I migrated again, replacing it with the current SiteUP! in order to avoid problems with a certain company that uses this type of prefix.

So if at some point you encounter the names JPanel, i-Mentha, or SiteUP!, they are all the same product at different times and in different coding forms.