Django Admin new look

[elky]

Hi guys,

I just made big front-end work on Django admin to make it look like new Django site - modern and clean.

I think it's user friendly now and not so scary for users. Need your opinion, guys.

See screenshots attached.

Just thinking what to do next - publish my own app or make pull request.

Thanks,

Alex

[Curtis Maloney]

Looks pretty slick, but brings with it all the hassles of the past attempts to re-skin admin: it breaks legacy custom pages.

I wish we could standardise a theming layer for admin... allow legacy templates, or switching to new, clean, themable templates...

Perhaps this could be integrated with the work to break down admin into a collection of CBGV?

... mostly thinking out aloud here :)

--

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-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
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/d3419ee7-2118-41ff-863e-55f4c05c43d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Collin Anderson]

Re theming layer: In theory (if you use collectstatic :) it should be possible to include an "app" that overrides the css files. I believe it the custom app would need to be placed above django.contrib.admin in INSTALLED_APPS. Or you can even override the files by putting them in a STATICFILES_DIRS. 

[Riccardo Magliocchetti]

Il 05/03/2015 00:37, Curtis Maloney ha scritto:
> Looks pretty slick, but brings with it all the hassles of the past attempts to
> re-skin admin: it breaks legacy custom pages.

AFAIK the admin never promised an "API" (if we can call html that), at the time
1.4 broke most of my custom admin templates.

> I wish we could standardise a theming layer for admin... allow legacy templates,
> or switching to new, clean, themable templates...

Elky demonstrated by changing only css that the current theme is themeable :)
Speaking of themes from my experience as django-admin-boostrapped maintainer
once you choose an ui framework you end up adding custom classes that of course
are different between frameworks. This means you have to redo all your templates
anyway. Which sucks of course.

> Perhaps this could be integrated with the work to break down admin into a
> collection of CBGV?

That sounds like pydanny's django-admin2

--
Riccardo Magliocchetti
@rmistaken

http://menodizero.it

[Ryan Allen]

These look very nice and are a step in the right direction. If you only overrode admin/css/base.css I see no reason why this change can't be made. Hanging on to the old design for legacy purposes has gone on long enough, it's time to update. I would make a pull request after ensuring the new design is fully tested and functioning properly.