5 ms·

There was a discussion a few years ago about revamping/updating the Django Admin - but I don't think it got much traction: https://groups.google.com/d/topic/dj

There was a discussion a few years ago about revamping/updating the Django Admin - but I don't think it got much traction: https://groups.google.com/d/topic/django-developers/Vozu6U3gz84/discussion https://groups.google.com/d/topic/django-developers/Vozu6U3g... My understanding is it's not something they care enough about yet to fix - or it's too hard/expensive. UPDATE: Also found this blog post from one of the core devs/founders: https://jacobian.org/writing/so-you-want-a-new-admin/ https://jacobian.org/writing/so-you-want-a-new-admin/

theptip 10y ago
> The admin may look simple on the surface, but it’s shockingly complex and represents a ton of work. This matches my experience. I can't escape the feeling that 90% of that complexity is irrelevant at best, and counterproductive at worst, for my current use-case -- but I haven't quite mustered the bravery to write my own custom admin site for my app. I wonder if DRF's CoreAPI schemas would make this easier, since you can now auto-generate a JS client for your API models, so you just need to wire up routers and views for your CRUD.
- sametmax 10y ago
  It's not. Every template, every view, every form can be overriden. And all of them have hooks on the admin config class to handle simple customization. The software internal is quite amazing and uses all Django's features in the book.
  - collinmanderson 10y ago
    > uses all Django's features in the book. Also, I think the admin traditionally has been a good driving force for feature improvement.
jldugger 10y ago
IMO, the proper method here is a frog boiling approach. Throwing it out and starting all over is bound to introduce regressions and even new user facing bugs. So we shouldn't of "steady, incremental improvement" as settling. But we could probably use more of those steady incremental improvements.
- collinmanderson 10y ago
  I personally agree: focus on the most important things, fix those, then move on to the next thing.

theptip 10y ago

> The admin may look simple on the surface, but it’s shockingly complex and represents a ton of work. This matches my experience. I can't escape the feeling that 90% of that complexity is irrelevant at best, and counterproductive at worst, for my current use-case -- but I haven't quite mustered the bravery to write my own custom admin site for my app. I wonder if DRF's CoreAPI schemas would make this easier, since you can now auto-generate a JS client for your API models, so you just need to wire up routers and views for your CRUD.

sametmax 10y ago
It's not. Every template, every view, every form can be overriden. And all of them have hooks on the admin config class to handle simple customization. The software internal is quite amazing and uses all Django's features in the book.
- collinmanderson 10y ago
  > uses all Django's features in the book. Also, I think the admin traditionally has been a good driving force for feature improvement.

jldugger 10y ago

IMO, the proper method here is a frog boiling approach. Throwing it out and starting all over is bound to introduce regressions and even new user facing bugs. So we shouldn't of "steady, incremental improvement" as settling. But we could probably use more of those steady incremental improvements.

collinmanderson 10y ago
I personally agree: focus on the most important things, fix those, then move on to the next thing.