August 23, 2008 at 02:10Why do you need a CMS?
Hello, Habrik!
The polemic that arose in the Personal Holivar prompted me to write this topic and continued in Why I Don't Like Russian Commercial CMS . I agree with the author of these topics in many respects, but still I consider it incorrect to compare CMSby length of piping , by work with templates and by classes, plugins, customization.
Initially, before developing any commercial software, the developer should (in theory) ask himself “What benefit will the purchase of my software bring?”.
Why are CMS / CMF written in principle?
In my opinion, there are such main goals:
In fact, of course, the goal is one - to increase profits. In this case, by reducing development and updating time. Only in the first case, due to the final implementation of the fields,
in the second, due to the speed of introducing popular scripts to the original design,
in the third, to speed up the process of writing original features, on which the bet is made on developed sites.
And when we say that WYSIWYG is terrible on the CMS template engine, or even better on the CMF, this is a banal unwillingness to delve into the goals of existing CMS and the criteria that are set for these CMS.
I have not yet met a CMS that has all three directions, and I have not really tried to do it.
Now I'm trying to design my CMS, but that's another story ...
You can still compare CMS by UI, but this will not affect the technical characteristics.
You can compare the possibility of caching, stability, the system of back-ups, templates, but if the question “Why do you need CMS?” Is not clarified All these specifications will only drive you into a dead end.
So, before looking for a CMS, think about what you need from it.
The polemic that arose in the Personal Holivar prompted me to write this topic and continued in Why I Don't Like Russian Commercial CMS . I agree with the author of these topics in many respects, but still I consider it incorrect to compare CMS
Initially, before developing any commercial software, the developer should (in theory) ask himself “What benefit will the purchase of my software bring?”.
Why are CMS / CMF written in principle?
In my opinion, there are such main goals:
- Building a marketing studio (“Any of your employees can update our site”)
- Automation of the layout process (“We make websites fast”)
- Automation of the programming process ("We write unrealistically complex things")
In fact, of course, the goal is one - to increase profits. In this case, by reducing development and updating time. Only in the first case, due to the final implementation of the fields,
in the second, due to the speed of introducing popular scripts to the original design,
in the third, to speed up the process of writing original features, on which the bet is made on developed sites.
And when we say that WYSIWYG is terrible on the CMS template engine, or even better on the CMF, this is a banal unwillingness to delve into the goals of existing CMS and the criteria that are set for these CMS.
I have not yet met a CMS that has all three directions, and I have not really tried to do it.
Now I'm trying to design my CMS, but that's another story ...
You can still compare CMS by UI, but this will not affect the technical characteristics.
You can compare the possibility of caching, stability, the system of back-ups, templates, but if the question “Why do you need CMS?” Is not clarified All these specifications will only drive you into a dead end.
So, before looking for a CMS, think about what you need from it.