2 ms·
I was discussing this the other evening. I've written a Django CMS that for in-house use. In some ways there's not much to it and it could easily be broken in
by andybak 14y ago
I was discussing this the other evening.
I've written a Django CMS that for in-house use.
In some ways there's not much to it and it could easily be broken into separate things:
Mainly:
1. WYSIWYG integration
2. An extensible 'Page' model
3. A way to generate site navigation
4. Admin customizations to make it more friendly for users.
In addition I reuse some excellent 3rd party packages.
Now - there are alternatives to all 4 things above that I could have reused but they were either lacking or not around when I started. I've ended up with something that covers my target market pretty well.
However I do feel there's room for another layer on top of Django - or maybe just some more reusable app conventions and a kind of 'CMS standard library' that made it more obvious to a newbie what to try first.
I know this isn't far from what Pinax was attempting but that seems to have gone very quiet.
Actually - several of the Django CMS projects are designed to be very lightweight and modular (FeinCMS is one - I borrowed some of their code and the author was very helpful) so maybe they already fit this bill.