Which CMS are modern in terms of architecture?

Question

CMS

There is a site of a large company, made on a not very popular CMS. The site needs a makeover in terms of usability and design. We are thinking of leaving the old engine or choosing a new one, but in order to decide, we need to understand how old the old one is. There is not enough own knowledge for evaluation...
In this regard, the question is - what are the important requirements for CMS from the point of view of architecture (well, for example, before everything was typeset with tables, and now with divs, support for HTML5, css3, frameworks, etc.)?

Answer 1

You are talking about the CMS architecture, but, clarifying, you mention only the layout side (table and block layout, html and css versions). If this is the only thing, then the question is, rather, exclusively to the design theme.
Are you really only interested in the front-end? Then CMS matters a little here. What theme you make up, this will be. Though on HTML 5, though on HTML 3.2.
There is only one important requirement - that the implementation suits you and your target audience. If the goal is to support as many environments as possible, support for IE5 and all sorts of Netscapes (I exaggerate, of course), then everything is necessary in the old fashioned way (with the exception of tables). If the target audience for the most part uses the current versions of browsers, then you can already play with HTML5, CSS3 and other magical things.
Even today it is fashionable to use all sorts of Responsive Design, and someone even thinks that without this the site is not modern at all, and it shouldn’t be like that. But it is also the taste and color.
If you are suddenly interested in the architecture of the CMS itself (its server part), then again it all depends on personal preferences. What you need, then there are important requirements.
It's like choosing a car. For someone a sports car: ride a heifer to clubs, and for someone a van: a heifer from a corral to a veterinarian to ride.

Answer 2

well, for example, before everything was typeset with tables, and now with divs,

Nonsense. Normal developers, and that way 10 years ago, typeset with normal markup. And now there are krivorukov who all shove in the table.

Answer 3

html, css, javascript, layout has absolutely nothing to do with CMS. Frameworks, in principle, too, if these are not php frameworks, but let's say css or js. To be honest, it is difficult to determine what requirements you need for a CMS without knowing your project, if only with a finger to the sky. Each cms is characterized by its own projects, and if you are making, for example, a news portal, then you need to choose DLE CMS, and if, for example, a blog, then Wordpress CMS and so on.

Answer 4

Hmm...you don't have enough knowledge for a basic trend assessment, and you offer your services to large companies???
However, I'm even glad that there are such companies, in fact, without them there would be no projects ala "Urgently fix a mistake in the site, the previous developer failed and merged"

Answer 5

MODX Revolution

Answer 6

Well, if the current CMS is developing, then probably it has not completely given up yet, and there is something special in it.
If you are not satisfied with usability - just audit popular CMS, and determine which one will be more usable for your purposes

Answer 7

I understand that you are interested in how easy it will be to pull a certain design on a CMS? I, as a coder, can advise you all the well-known Joomla, the latest version (like 4, I don’t remember exactly). Since the latest version, their layout has significantly improved, and in general it has become pleasant to look at the insides.

Answer 8

The main task of CMS follows from its name - site content management.
Indeed, this has nothing to do with the layout/design of the client side. Only to the admin. If the CMS meets your requirements related to content management and functionality refinement, of course, transferring it to money, then there is no point in changing it.
Switching to another CMS is a very resource-intensive task. Whether it will pay off in the long term in terms of the difference in the cost of supporting the old and the new is up to you to decide.

Answer 9

do not bother with this if you do not program yourself,
otherwise you will eventually have to take on faith this or that Internet statement "the CMS has such and such a modern architecture", and what will it give you practically? It can lead to a common mistake: choosing a tool for a performer => will increase the cost and delay development, worsen the result (after all, you and your visitors need the result, and not just faith in some invisible "architecture").
First of all, contact responsible and competent people whom you trust and who will not throw you in the long run, and they will choose from their experience what is convenient for them.
But if in general terms, all modern web applications are based on the MVC model, aimed at the maximum separation of content and functions for working with it (separation of templates, each module, etc). You can, if necessary, clarify how this principle is used in the selected product.

Answer 10

Drupal/MODx... though both are CMFs rather than CMSs.