Difference, which is better/more convenient Django-cms OR FeinCMS OR Mezzanine?

Question

Django

That's the question itself: who has worked with various CMS based on the Django framework, which is better / more convenient Django-CMS , FeinCMS or Mezzanine ? Maybe there are some others?
It is also important to have topics for them, not everyone uses bootstrap, or am I misunderstanding everything?
I read the review at www.mixedcase.nl/articles/2011/01/28/django-cms-vs... but it's already 4 years old and the progress is not standing still. And I would like to learn from practitioners in Russian on the topic of the issue. I think it will be interesting not only to me alone, but to many, especially beginners

Answer 1

It seems to me that "better" or "more convenient" are subjective metrics. And not very absolute. For example, grappelli (an application that changes the appearance of the admin panel) infuriates me, but on the contrary, someone likes it. Mezzanine, as far as I remember, grappelli uses. It will seem to me the wildest minus, and to someone plus.
Personal experience: I had a chance to work quite closely with django-cms and fein. In general, they work on the same principle, although they use different terminology (django-cms plugins that are placed in placeholders to expand the functionality of the page, and fein - content types and areas, respectively), the essence is about the same. Albeit implemented slightly differently.
Now the key difference between djnago-cms and fein is that the first, starting from version 3.x, has switched entirely to front-end content editing. There is no admin panel as such, instead a redirect to a page with editing enabled. And Fein is managed from the admin panel, like earlier versions of django-cms.
For the programmer, both cms are relatively convenient and easy to develop and provide an interface for writing plugins (or content types, depending on). But if you go deep under the hood, then in django-cms everything is much more complicated in terms of models and relationships. Therefore, a very wise move on the part of its developers was to provide a "low-level" api with functions like create_page (), which actually creates a dozen records in ten tables :-)
Regarding the convenience of editing content, again subjective: both are terrible. Probably fane even more so. But at the same time it is more obvious. You can’t say the same about front-end editing of django-cms, where you can’t figure it out without a pint: first put the page in edit mode, then switch the incomprehensible content \ structure toggle switch (or something like that, I don’t remember exactly now), then select the plugin to be edited. .. then don't get confused by the save and publish buttons, and so on. My colleague is of the opinion that it is simply not possible to show this to users.
By the way, the user can easily break the site tree (up to calling the 500th instead of visiting any of the pages), simply by actively dragging the nodes of the tree back and forth in the admin panel. This applies to both fein and django-cms.
As for the mezzanine. I remember this: he uses grappelli, for some reason there is a built-in store and blog, which are not needed on every site. I didn’t remember the pluses, I demolished it. Although now, having opened the documentation for the sake of curiosity, I see something about custom content types, so it will probably be the same as fein / django-cms, but in grappelli greenish tones. And with the store :-)

Answer 2

> Maybe there are some others?
There is also https://wagtail.io/
Review - djbook.ru/forum/topic/3214/#post-21228