G'day Brent,
this is an obvious question:
I too have come to node from django, and the first thing I wanted was a handy admin:
I'm mostly doing simple website projects where half the effort can be in the client facing admin pages.
A quick look at the express documentation will reveal that it's ORM agnostic.
The view rendering example code snippets use literal objects: where they gonna come from?
Our admin interface is gonna have to either pick a store to administer, or define an ORM.
Either way, that isn't gonna just sit on top of express, because this decision will also tie into how we collect objects to feed to the view renderer.
this realisation goes to Django's structure as an end to end solution:
logically, the admin interface seems like a layer, but practically, it is entwined with other opinionated features and components of the (wonderful) monolith, that simply aren't defined by express.
So, short answer: no, django admin isn't going to slot on nicely to express for ya.
I've put some time into making a very simple admin for express on mongoose. It's good enough for my simple requirements, but I've made some decisions that will make it unlikely to just fit nicely with whatever else you're doing.
(eg: I'm not using views - I like anti-templating)
but if you're gonna put some effort into this, you might pick up some clues in the admin section of
www.justsayno.de
Anybody got any other directions on this?
-= jTNT