> The admin isn't "broke" in that is still does what it was designed to do in 2005 or whatever.
The django admin was designed to do is basic CRUD operations. It does a good job of that. > We simply stopped including the admin in every project we build—and I mean deleting every admin.py and taking admin out of urls.py—because it invariably causes more problems than it solves. What problems does the admin interface cause? Would these problems be solved with modals? I think explaining these problems you mentioned can shed light on what improvements can be made. > If we have to do anything database-related, we either do it directly or use the Django shell. If clients want any kind of "admin"-like dashboard or whatever, we build it from scratch. What limitations does the admin interface have that requires using the Django shell or adhock "admin"-like interfaces instead? On Thu, Feb 26, 2015 at 12:40 PM, Chris Foresman <[email protected]> wrote: > > > On Thursday, February 26, 2015 at 10:25:02 AM UTC-6, Thomas Leo wrote: >> >> I've opened a ticket [1] to implement the popups in the admin as modal >>> instead >>> of windows. I'm no UI/UX expert but modals are more or less the standard >>> today, >>> windows looks like a relic from the 2000s. >> >> >> If it ain't broke don't fix it. The django admin is awesome, the reason >> it hasn't changed much is because it doesn't need to. Google.com's home >> page still more or less looks the same as it did in 2000. >> > > > The admin isn't "broke" in that is still does what it was designed to do > in 2005 or whatever. I don't believe that fact supports your assertion that > it doesn't need changed, and even most of the Django maintainers agree the > existing UI isn't "awesome." Functional, to a specific end, yes, but not > "awesome." Nearly everyone I know that uses Django agrees that the admin > interface could use improvement. > > We simply stopped including the admin in every project we build—and I mean > deleting every admin.py and taking admin out of urls.py—because it > invariably causes more problems than it solves. If we have to do anything > database-related, we either do it directly or use the Django shell. If > clients want any kind of "admin"-like dashboard or whatever, we build it > from scratch. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/b38JElfE3wk/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/23deeacb-b344-4c32-a1d3-7ed2a4964ef2%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/23deeacb-b344-4c32-a1d3-7ed2a4964ef2%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJJLp8UHOd489qu_wN2xPRvwfrnvTsTAwJ0s9uhuYo54mHAPWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
