While I think it's true that a process centric workflow (wizards, or hubs anyone?) would be incredibly useful, that does not take away from the fact that the model centric admins are also incredibly useful, and time saving. It's so easy to add search, sorting, bulk actions, etc to an admin--these are things I've often spent days or weeks working on in other systems. With django it is often a matter of minutes to add these incredibly common features. This is probably one of my favorite things about the django framework.
On Wednesday, February 10, 2016 at 5:33:03 PM UTC-8, Curtis Maloney wrote: > > > > On 11/02/16 00:55, Andy Baker wrote: > > I can't help but feel that the "admin is very rudimentary and hard to > > customize" is perpetually overplayed by many in the community. Maybe I'm > > suffering Stockholm Syndrome but I'd like to raise a dissenting voice. > > I must admit I'm a large proponent of warning against getting caught up > in "Admin as my management console". > > As customisable as it can be, I find the problem to be it is a > data-centric view of your system, closely tied to the database models. > > IMHO a management interface for site should be a _process_ centric view, > abstracting away the implementation details of tables and fields. > > Perhaps a better way to think of it as the difference between a > "management" and a "maintenance" interface. > > True, in a lot of cases these can be the same thing, and for simpler > sites Admin works "just fine". However, I've been on too many projects > that wind up spending a lot of time and effort customising Admin to do > things that would have been simpler in a custom view. > > Worse still, I've seen projects alter their schema design to accommodate > Admin's limitations [like lack of nested inlines] > > Is it possible to add other views to admin? Sure... though it's not > clear, or well documented. > > Can documentation alone overcome this problem? I'm not convinced it can. > > For some years now I've been proposing an investigation into slicing > Admin into two layers: a base "management interface framework" layer, > and "admin" built atop this framework. > > Then we can keep providing the Admin we all know and love, and also make > it easier for people to build their own management interfaces. > > However, I don't currently have the time [or admin familiarity] to > undertake this work. > > -- > Curtis > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/26ee6e6b-f5dd-4959-a8d9-d1be6acfad4b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
