+1 -- Aymeric.
> On 17 févr. 2016, at 18:16, Marc Tamlyn <marc.tam...@gmail.com> wrote: > > That looks like a good balanced message to me. > > On 17 February 2016 at 16:57, Tim Graham <timogra...@gmail.com > <mailto:timogra...@gmail.com>> wrote: > Here's another try for the docs: > > One of the most powerful parts of Django is the automatic admin interface. It > reads metadata from your models to provide a quick, model-centric interface > where trusted users can manage content on your site. The admin's recommended > use is limited to an organization's internal management tool. It's not > intended > for building your entire front end around. > > The admin has many hooks for customization, but beware of trying to use those > hooks exclusively. If you need to provide a more process-centric interface > that abstracts away the implementation details of database tables and fields, > then it's probably time to write your own views. > > > On Friday, February 12, 2016 at 4:30:07 AM UTC-5, Andy Baker wrote: > > However, we NEVER had a client that was sufficiently familiar with what a > > database is or how data modeling works for this to ever suffice. > > I've got more than two dozen non-technical clients happily using the admin. > They also have no familiarity with data modelling but I'm not quite sure how > that would help or hinder them. The concept of a filterable list view and an > editable form luckily doesn't require discussing 4th normal form or the > benefits of relational algebra ;-) > > On Thursday, 11 February 2016 19:47:43 UTC, Chris Foresman wrote: > FWIW, we used to tell clients that Django offers a basic admin interface "for > free". However, we NEVER had a client that was sufficiently familiar with > what a database is or how data modeling works for this to ever suffice. The > first thing we always do on new project is immediately disable the admin and > simply design APIs that allow our front-end teams to build some kind of > custom dashboard/admin interface. > > IME, the admin is "sufficient" for sysadmins or technically experienced > users, but in practice those are few and far between. > > > > On Thursday, February 11, 2016 at 12:08:08 PM UTC-6, bliy...@rentlytics.com > <> wrote: > 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 > <mailto:django-developers+unsubscr...@googlegroups.com>. > To post to this group, send email to django-developers@googlegroups.com > <mailto:django-developers@googlegroups.com>. > Visit this group at https://groups.google.com/group/django-developers > <https://groups.google.com/group/django-developers>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/363c6710-b75f-40d5-a790-f0ab98aa5635%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/363c6710-b75f-40d5-a790-f0ab98aa5635%40googlegroups.com?utm_medium=email&utm_source=footer>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > 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 > <mailto:django-developers+unsubscr...@googlegroups.com>. > To post to this group, send email to django-developers@googlegroups.com > <mailto:django-developers@googlegroups.com>. > Visit this group at https://groups.google.com/group/django-developers > <https://groups.google.com/group/django-developers>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAMwjO1Gku272bs0uUOqsTV7jAYX_4cPHqdKhoVyCcQZEuW4Mag%40mail.gmail.com > > <https://groups.google.com/d/msgid/django-developers/CAMwjO1Gku272bs0uUOqsTV7jAYX_4cPHqdKhoVyCcQZEuW4Mag%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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/9F55A1A0-12C4-4250-8D9C-FC6A21CA666B%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
