[rxdazn]

My main problem with Django CMS frameworks is that they all use the django admin which quickly becomes a PITA when you want to modify it. I'm really starting to prefer rolling my own easy to use admin interfaces to trying to override the django admin.

[maheart]

Wagtail (https://github.com/torchbox/wagtail/) does not use the Django admin. It leaves it completely alone. It really is just another Django app. Highly recommended.

[andybak]

I strongly feel the exact opposite. I've worked with the Django Admin extensively since 0.98 and it gets more flexible and easier to customize with every release.

There's an astonishingly large ecosystem of widgets, extensions and additions and having a single point of integration that (mostly) everyone agrees on allows them all to work fairly well together.

There are things that I wish could be improved about the admin - mainly to do with the slightly old-school HTML and CSS behind it - but there are so many points where you can override, replace and extend that the good outweights the bad.

[crdoconnor]

>There are things that I wish could be improved about the admin - mainly to do with the slightly old-school HTML and CSS behind it - but there are so many points where you can override, replace and extend that the good outweights the bad.

I use this: https://github.com/django-admin-bootstrapped/django-admin-bo...

It seems to work pretty well.

[andybak]

Except all the HTML is now different to the standard admin and lots of 3rd party apps break.

Unfortunately - there is a limit to how much you can alter the admin HTML without this problem. My own admin skins have been CSS only precisely to avoid this.

[collyw]

I love the Djqngo admin, and use it a lot at my day job, but it does seem to be a PITA to try and do non standard things with it (say add an extra button). And it always looks like the Django admin - its a great set of sensible defaults, but often you don't want that.

I am currently trying to learn the ins and outs of generic views with djang-extra-views, so that I can hopefully do as much, but without the restrictions of the admin.

[ojii]

django CMS 3 [1] still uses the underlying admin system (for it's CRUD views etc), but moved all editing into the frontend, thus making it more friendly to content editors.

[1] https://www.django-cms.org/en/

[subleq]

Widgy doesn't require the Djange admin. You can attach a widgy content editor to any model.

[jnowlan]

So widgy could by used with Pyramid via sqlalchemy?