[mattwestcott]

On the 'framework on top of the framework' point - one thing we've aimed to do with Wagtail is to preserve Django's approach to models, templates and so on, rather than falling into the 'inner platform' trap and building a totally new system that just happens to use Django under the hood. So, for example, page layout is still done with Django's template system, and new page types are just Django models with some additions. As a result, using Wagtail is actually not massively different to the DIY route, at a functional level - but you get the extra bells and whistles like revision tracking and workflow as well.

[andybak]

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

[xaritas]

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.

[andybak]

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.