Why do you need a CMS?

Hi, Hubrick!

It prompted to write this topic controversy that arose in Personal Holivar and continued in Why I do not like Russian commercial CMS . I agree with the author of these topics in many respects, but I still think it is wrong to compare CMS by the length of the pipisk , by working with templates and by classes, plugins, casting.

Initially, before developing any commercial software, the developer should (in theory) ask himself "What benefits will the purchase of my software bring?".
')
Why are CMS / CMF written in principle?
In my opinion, there are such main goals:

1. Building a marketing studio ("Our website can be updated by any of your employees")
2. Automation of the layout process ("We make websites quickly")
3. Automation of the programming process ("We write unrealistically complex things")

In essence, of course, the goal is the same - to increase profits. In this case, by reducing the time to develop and update. Only in the first case, due to the final implementation of the fields,
in the second, due to the speed of implementation of popular scripts on the original design,
in the third, to speed up the process of writing original features, on which the emphasis is being placed on the developed sites.

And when we say that WYSIWYG is terrible on the CMS template engine, or even worse on CMF, this is a trivial unwillingness to delve into the goals of existing CMS and the criteria that are set for these CMS.

CMS which has all three directions, I haven’t met yet, and I haven’t tried very hard to do it.
Now I am trying to design my CMS, but that’s another story ...

You can also compare the CMS UI, but it does not affect the technical characteristics.
You can compare caching, stability, back-ups, templates, but if the question “Why do you need a CMS?” Is not clarified, all these specifications will only drive you into a dead end of choice.

So, before looking for a CMS, think about what you need from it.

Thanks to everyone who read me.