Live data from Hacker News

A new Django content management system

github.com

41–43 of 43 posts

Re: A new Django content management system

#41
post #24

Paraphrasing Bruce McKinney on Visual Basic (who was probably paraphrasing someone else): "Django-based CMS systems make the easy easier and the hard impossible". I worked with Django for about 4 years of my life, maybe more if we consider some proof-of-concept projects. Every single 'framework on top of the framework' (with the exception of Django REST Framework) I've tried has been 'almost perfect', but that little…

For a site with a handful of pages and a single author who's happy to use django.contrib.admin I agree with you that plain DIY Django will probably get you there more quickly. But Wagtail (and other Django CMSs) gives you a lot more than that: - a fast, intuitive content authoring experience - preview / submit / moderate / publish workflow - a UI which scales to very large numbers of authors, pages, images - powerful…

Hi!

Sorry, I didn't mean my comment to come through as criticism to this particular project. I meant it as a more of a warning to people who might be tempted to use such a complex system for something like running a small few entries in their website. Chances are the effort to integrate it would be bigger than just writing a minimalistic thing in the existing codebase.

I agree that systems like these have a place if what you want is something akin to Drupal (but with a nicer codebase.)

Re: A new Django content management system

#42
post #40
post #37

Earlier quoted context omitted.

It's a shame you didn't attempt to integrate with the standard admin. That alone makes you slightly 'an island apart' as I now face the challenge of either: a) build my own CRUD for parts of the system that aren't directly related to the CMS (products, crm etc etc) or b) rely on integration with your admin - which I'm guessing isn't as extensible or mature as Django's

Wagtail's authoring interface and Django's admin coexist. I believe the demo sets up the Wagtail interface at /admin and puts the standard admin at /django-admin. Presumably you can change those in your urls.py to whatever you like.

Two admin interfaces with different appearances and UI conventions isn't a terribly optimal user experience.

If Wagtail even attempted to smooth the differences between the two (i.e. a custom skin and some customizations to the default admin to make them more similar) then it might be a bearable compromise.

Post reply on HN