Imagine, you need an online store without integration with 1C, and you decide on the base (engine), on what to make it? There should be standard options – catalog, filters, selections, export from Excel, shopping cart, delivery / payment and much more. They call you some incomprehensible words: Joomla, Opencart, Virtuemart and a bunch of others.
These are all – engines, platforms on which sites are built. They are called CMS or, more simply, management systems. In addition to CMS, stores and sites can be made on so-called frameworks – this is something like the Windows operating system, on which additional modules are installed, and a finished project is assembled from them like building blocks.
As a result, the CMS already has all the ready-made functionality at once, but in the framework it needs to be assembled. How are the approaches different and why is the framework better?
Let’s say the functionality of your store is standard, it is available in almost all ready-made online stores (CMS) such as Opencart, Virtuemart, Prestashop, etc. functions in the admin panel.
In fact, every such store (this also applies to ready-made CMS such as Joomla, WordPress, etc.) is an all-in-one thing.
Those. we tried to cram as many functions as possible into one system, 90% of which will not be useful to you at all. As a result, nothing can be found in the menu, the controls are inconvenient, but the most interesting thing happens when we “try to take off with all this nonsense.” As you know, if something in the system can break, then it will break.
If there is a lot of things in the system that can break, the chances of breakage are much higher. In addition, all these extra modules do not hang like a dead weight, they cannot be taken and turned off. They take up server resources, affect the speed of opening pages, and affect overall reliability and security.
A framework project consists of a core and modules. In this case, only those modules that are currently needed are hung on the kernel. If you need a new module, it is hung on the core and a new section appears in the admin panel.
In fact, it resembles an operating system - you do not install everything on your computer, but only those programs that you need. And all that is superfluous - delete so that the computer does not slow down.
Projects on the framework are arranged in the same way – nothing more! Only necessary modules that have been tested and debugged many times. Only the necessary functions in the admin panel. If, for example, you do not like the page editor or the feedback module, it simply changes to another, which cannot be done in the CMS.
As a result, projects on the framework are much more reliable, faster and safer (there is practically nothing to break there, unlike a CMS). The server load is much less than when working with a CMS, the site works faster, the database can be larger, the site can withstand much more simultaneous visits, hosting and technical support costs are lower.
Products based on the framework are much more flexible – as from bricks you can assemble any configuration of a project or store, add non-standard functions that are simply not in the CMS, make your own modules, constantly modernize the product by adding new modules and capabilities.
Absolutely any design can be pulled onto a framework, unlike a CMS. But the main thing is simplicity and convenience – it will be much easier for you to master the product on the framework than the product on the CMS due to the fact that in the admin panel there is only what is needed, and nothing more! A person without Internet knowledge easily masters the admin panel of the framework, and with difficulty the admin panel of Joomla and other similar systems. hosting and support costs are lower.
Products based on the framework are much more flexible - as from bricks you can assemble any configuration of a project or store, add non-standard functions that are simply not in the CMS, make your own modules, constantly modernize the product by adding new modules and capabilities.
Absolutely any design can be pulled onto a framework, unlike a CMS. But the main thing is simplicity and convenience – it will be much easier for you to master the product on the framework than the product on the CMS due to the fact that in the admin panel there is only what is needed, and nothing more!
Projects on frameworks are somewhat more expensive to develop than projects on CMS, but convenience, reliability and speed more than justify the costs incurred, because you get the most effective solution that works at 100% of its capabilities and at maximum speed, unlike bulky, “fat” “CMS slowing down the server and the project as a whole.
That is why we try not to work with classic CMS, besides, where necessary, we do almost all our projects.
We do not save on the customer and are not ready to offer a low price to the detriment of quality, for us the main thing is that your project works stably, reliably, efficiently, and you feel comfortable working with it.
We do not want you to be disappointed later, long-term cooperation is important for us.
Where necessary, we use 1C-Bitrix, it is devoid of many CMS problems, but all the same, projects on frameworks are faster, less demanding on hosting and easier to learn. We also use the MODX Revolution system, which combines the advantages of a CMS and a framework.