News for hackers. Stuff that matters.
Re:Django UI in 2005 vs. Django UI in 2014 by stuaxo on Thursday September 18, 2014 @12:09PM (#8335975)
I don't know about generic, it's not that extensible, it can be a pain when you want to write widgets outside of what it does.

The same is true about other parts of Django. It's still quick to get things running, and there is a great ecosystem.

[EDIT] Grapelli is a great example of how not-extensible the admin is - to do something that should just be a reskin, they have to copy large parts of the admin code and then adapt it.

The admin should be built in a way so that something like grapelli is just a some new CSS. [/EDIT]

Re:Django UI in 2005 vs. Django UI in 2014 by andybak on Thursday September 18, 2014 @01:33PM (#8336497)
Grapelli chose not to stick to pure CSS. It's not a trade-off I think was worth it as they have no cut themselves off from much of the 3rd party admin extension ecosystem - unless those apps actively do a 'Grapelli version'

Pure CSS skins are a bit more work and you occasionally have to choose between overriding more template code than you'd like - or doing a sneak bit of jQuery DOM manipulation - but it's a better bet long term.

A really simple fix for the core Django team would be to add a heap of {% block %} tags into admin templates so that we can selectively inherit and override.