Answer the question
In order to leave comments, you need to log in
What properties and capabilities should a modern CMS have?
Over the course of several years, I completely rewrote the CMS 3-4 times. This was mainly due to the inconvenience of the old version, but now the version is convenient in terms of rapid development, but something in it still does not become outdated for me.
Therefore, I decided to ask you, what properties and capabilities should a modern CMS have? What should be present in it and what should be absent? Modular system or not?
As an example, my thoughts:
- The ability to relatively simply and quickly develop sites of any complexity
- Unlimited possibilities
- Multi-site
- Support for multilingualism
- Upgradability
- Ease of use in maintenance and operation
PS Please do not offer to refuse to create a bicycle and use a third-party CMS.
Answer the question
In order to leave comments, you need to log in
>> - Unlimited possibilities
after this point, there is no point in reading further :)
>> What properties and capabilities should a modern CMS have?
All that Drupal can do, only easier to work with and completely redone multilingual
in fact, no one answered anything, okay, I'll try to carefully insert my opinion:
1. There should be an abstraction layer for working with databases, files, etc
2. There should be a good simple template engine (with php-like syntax) with helpers
3. It should be implemented mvc design pattern
4. I would like AR, of course
5. Tree structure of the site with unlimited nesting
6. Ability to manage the rewrite module
7. Adequate caching system
Think about those who will pull the project after you if the client terminates the contract. Often you have to deal with sites based on such mega-cool CMS, which can do everything except how to quickly export all the content.
If the CMS is self-written, it should be able to conveniently export itself. Well, for example, something to import into the next super-CMS.
don't use php, nothing else matters.
as frameworks, pay attention to aida/web , seaside
Integration with social networks, OpenID and more.
AJAX
Plugins, modules
Once, in favor of simplicity and performance, I abandoned the modular system, but now I understand that this is a necessity.
Maybe you have some options how to implement a modular system?
Just please, do not send other CMS to watch, everything is different for everyone. I would like to hear your opinion.
It must be understood that the requirements for the system are not single-level. Above the architectural and functional requirements, there are also business requirements.
Business requirements, by the way, are also heterogeneous. There is a side-implementer, and there is a side-customer.
So, from a business point of view, CMS is required, first of all, to ensure the development efficiency in terms of time and budget, the minimum cost of ownership, reliability and security.
The ability to create arbitrary entities with an arbitrary set of attributes by a user (webmaster, not a developer). The ability to create arbitrary relationships between entities (both deterministic (explicitly set a la consumables for such and such a printer) and automatically calculated (a la “also choose”)), and not just a one-dimensional hierarchy (aka catalog / categories) and /or "tag cloud". Flexible routing. Support for all this in templates.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question