What kind of content organization in CMS is more convenient?

Question

CMS

You can give the user the ability to assemble a document from various kinds of building blocks (as I understand it, Drupal works this way). In this case, the load on the administrator (author) increases.
Or it's stupid to use an "iron" scheme, i.e. the document in the blog should consist of strictly defined fields, and any changes in the functionality through plugins. In this case, there is less flexibility, but the system seems to be closer to the user.

What do you advise? Interested in both the opinion of programmers and users of such systems.

Answer 1

In Drupal 6, nodes have strictly defined fields. And there is a plugin that allows you to add the next building blocks - CCK, you need to download and install it separately ...
In Drupal 7, this module is not just delivered out of the box, but integrated with the system.
So some intermediate option turns out;)

Answer 2

there are two options for drupal:
1) drupal + CCK
we create the content type we need
and already add the fields we need to the type (next blocks-bricks)
then we can create nodes of this type
2) drupal + self-written module
write a module that adds the necessary us fields.
then we can create nodes of this type

Answer 3

Drupal (with cck) works a little differently, as far as I remember - from blocks-bricks (or rather fields of various types), it usually allows only the administrator to create a new type of document, and other users (authors) can create documents of this type - fill in mandatory fields (with restrictions set by the administrator), whether or not to fill in optional ones ... But adding your own or, at least, not filling in the mandatory ones will not work for the author (with default rights). In general, everything is in the tradition of relational databases with a rigidly defined schema.

Answer 4

If the system is aimed at the mass user, everything should be tough.
If the system is aimed at qualified developers, everything should be as flexible as possible.
Who are you doing for?

Answer 5

IMHO, if you are writing a CMS, then the best option would be the following - a rigid form for the page (almost direct display in the database is better) + the ability to add additional fields (such as key-value, then it is easy to display this in the template through {additional field key}) + form builder and many widgets. With a certain degree of rigor, almost anything can be implemented. For content, it would be cool to have a rich editor that will work with the media library. Look at Wordpress (although not everything that I described, it can out of the box).
Another thing is if you want to write CMF, then you need to enable coding from the admin panel, but such an admin panel is not suitable for the user.
Check out Modx.

Answer 6

I have been working recently on modx - both the programmer and the user are satisfied with everything. in addition, access policies are very finely tuned in Revo, where you can remove all unnecessary fields for the editor and leave a completely convenient interface for editing materials.

Answer 7

in phpMyEngine, I implemented everything like this:
there is a base class Record , which stores the main data about the record - id, tags, rating, etc., Record also has two special fields - mutagenType and mutagenData . mutagenType specifies the type of the mutagen (for example " staticpage ", " blogpos ", " category ") and mutagenData loads the properties of that mutagen. The mutagen itself is stored in "etc/mutages" and is a JSON file with a description of the properties and their behavior. And in the admin panel, a form for editing is also auto-generated :)
If it's interesting, I can soon start a series of articles in "I write CMS