What is the organization of content in the CMS is more convenient?


Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
18 views
It is possible to provide the user with the ability to assemble a document from different kind of blocks-bricks (as I understand it, Drupal works that way). In this case, increases the workload of the administrator (the author).
Or just use the "iron" scheme, i.e. the document in the blog should consist of strictly defined fields, and any changes to the functionality via plug-ins. In this case, less flexibility, but the system is kind of like closer to the user.

What would you recommend? Interested in how the opinion of the programmers and users of such systems.
by | 18 views

7 Answers

0 like 0 dislike
6m in Drupal the node is strictly defined fields. And there is a plugin that allows you to add new blocks-bricks — CCK, it is necessary to download and install separately...
7m in the same Drupal this module is not just comes out of the box, and combined with the system.
\r
So some intermediate version turns out ;)
by
0 like 0 dislike
for drupal are two options:
1) drupal + CCK
we create the necessary content type
and by the type dobavlen we need a field (regular blocks and bricks)
then you can create nodes of this type
\r
2) drupal + hand module
write a module with which a certain type of content adds we need fields.
then you can create nodes of this type
by
0 like 0 dislike
Drupal (cck) bit is not working, as I recall — blocks of bricks (or rather fields of different types), it usually allows only the administrator to collect a new type of document, while other users (authors) can create documents of this type to fill in the required fields (defined by the administrator restrictions), to fill or not optional... But add your own, or at least, not to fill in the required author does not (by default rules). In General, all in the tradition of relational databases with rigidly predetermined scheme.
by
0 like 0 dislike
If the system is focused on mass — everything has to be hard.
If the system is aimed at skilled developers, everything has to be as flexible as possible.
And you for whom you're doing?
by
0 like 0 dislike
IMHO, if you write CMS, then the best option would be the following — a rigid form for the page(better almost direct mapping in the database) + the ability to add additional fields(like key-value, then the template is easy to deduce that {misc key}) + form Builder and many widgets. With a bit of rigor, you can implement almost everything. For content, that will be nice to have a rich editor that will work with the media library. Look at Wordpress(though not all that I have described, he can out of the box).
\r
Another thing is if I want to write a CMF, then you need to make the possibility of coding from the admin, but this admin will not do.
Look At Modx.
by
0 like 0 dislike
last time in modx as a programmer and user I was happy with everything. besides, the Revo is very thin configured access policy where you can remove the editor all the extra fields and leave quite a convenient interface for editing content.
by
0 like 0 dislike
in phpMyEngine I implemented all this:
is the base class Record, which stores basic data about a record — id, tags, rating, etc., and Record there are two special fields — mutagenType and mutagenData. In mutagenType select the type of mutagen (e.g. "staticpage","blogpos","category"), and in mutagenData load the properties of the mutagen. The mutagen is stored in "etc/mutages" and represents a JSON file with description of properties and their behavior. In the admin, still autogenerates the mold for the edit :)
If interested, I may soon start a series of articles in "I'm writing a CMS"
by

Related questions

0 like 0 dislike
2 answers
0 like 0 dislike
5 answers
0 like 0 dislike
3 answers
0 like 0 dislike
4 answers
110,608 questions
257,186 answers
0 comments
25,337 users