Perfect CMS, what is it?
The invention of PHP by programmers, which means writing your own CMS, is probably the cornerstone for developers and users. There are sites such as cmslist.ru , smagazine.ru , and just the number of CMS for the last half year, the year has increased by an order. Actually, the analysis of this situation is a completely different tale. But building an ideal CMS or some higher principle of building one that aggregates most of the advantages and minimum of flaws in itself is a question, the answer to which is interesting, probably, not only for me, but for many developers.
Preamble. (Part 1)
CMS - Content Management System [ WiKi ], based on its name, says a lot already :)
Here you can probably immediately assume the division of CMS based on the content used:
plain text;
Further, delving into the expansion of work with users, we can assume the need for additional services - registration (personal account), an online store, the ability to leave comments, create polls, forum etc.
')
A few words about typical terms of use and types of customers. I'm not afraid of such a division of customers into two large groups such as:
This is a seemingly stupid and unformatted division, but let's see in more detail what is meant, for it is not easy to express the idea clearly in two words:
In general, such a division of customers causes another type of CMS division, namely:
ease of implementation and further development;
or ease of management, in the form of easy writing of content, and nafig all add. modules, for difficult;
Well and, the most, unobvious division according to the type of admin device and the CMS engine itself. CMS representing the formation of the page on the fly, by assembling a template by means of a scripting language from the database;
and a number of CMS based on the publication of pages in static html;
Total:
The question, gentlemen habracheloveki, whether there is a place to be all of the above and whether further consideration of the prerequisites for the creation and options for building some kind of ideal CMS will be interesting?
UPD0:
The absurdity of the ideal was clear before writing, it is clear that without the transformation of a thought form into a result, the ideal is doubtful. However, in my opinion, such a concentration of thought that would not eventually turned out to be garbage still needs to be achieved, but this is already a philosophy.
But, the ideal was presented to me as an aggregation of the most optimal solutions, and first of all for the developer, it was with this that the habra community tried to clarify the approaches and implementations, the habra community as the developer community. And the comments from the customer turned out in the comments, offensively ...
Preamble. (Part 1)
CMS - Content Management System [ WiKi ], based on its name, says a lot already :)
Here you can probably immediately assume the division of CMS based on the content used:
plain text;
- structured data (news etc.);
- A large number of structured data (product catalog with characteristics), combined with common data (reference books).
Further, delving into the expansion of work with users, we can assume the need for additional services - registration (personal account), an online store, the ability to leave comments, create polls, forum etc.
')
A few words about typical terms of use and types of customers. I'm not afraid of such a division of customers into two large groups such as:
- those who want a website and management tool, but have little idea how all this should be;
- and those who use CMS in full;
This is a seemingly stupid and unformatted division, but let's see in more detail what is meant, for it is not easy to express the idea clearly in two words:
- There are such customers who have a lot of information for the site, management of this information is planned by the secretaries or by the developer, development of new functionality is not planned, and if it is planned, then at any expense by CMS developers.
- And there are, for example, those who have specialists in their own power to fill, maintain, develop.
In general, such a division of customers causes another type of CMS division, namely:
ease of implementation and further development;
or ease of management, in the form of easy writing of content, and nafig all add. modules, for difficult;
Well and, the most, unobvious division according to the type of admin device and the CMS engine itself. CMS representing the formation of the page on the fly, by assembling a template by means of a scripting language from the database;
and a number of CMS based on the publication of pages in static html;
Total:
The question, gentlemen habracheloveki, whether there is a place to be all of the above and whether further consideration of the prerequisites for the creation and options for building some kind of ideal CMS will be interesting?
UPD0:
The absurdity of the ideal was clear before writing, it is clear that without the transformation of a thought form into a result, the ideal is doubtful. However, in my opinion, such a concentration of thought that would not eventually turned out to be garbage still needs to be achieved, but this is already a philosophy.
But, the ideal was presented to me as an aggregation of the most optimal solutions, and first of all for the developer, it was with this that the habra community tried to clarify the approaches and implementations, the habra community as the developer community. And the comments from the customer turned out in the comments, offensively ...
Source: https://habr.com/ru/post/51820/
All Articles