#29999: Include overriding admin site to tutorial
-------------------------------------+-------------------------------------
Reporter: Jan Musílek | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 2.1
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jan Musílek):
Replying to [comment:1 Tim Graham]:
> I don't see overriding the admin site as a necessary requirement.
`site.site_header = '...'` still works fine.
Sure, it isn't necessary, I just see it as a new obvious way how to
customize admin site in broader context. Is it the recommended way? I
thought it might, which is why I proposed this change in the first place.
Would it be better if we changed **and** to **or**?
* We use this approach to teach you how to override templates. In an
actual project, you would probably
[https://docs.djangoproject.com/en/2.1/ref/contrib/admin/#overriding-
default-admin-site override the default admin site] **or** use
[https://docs.djangoproject.com/en/2.1/ref/contrib/admin/#django.contrib.admin.AdminSite.site_header
django.contrib.admin.AdminSite.site_header] attribute to more easily make
this particular customization.
--
Ticket URL: <https://code.djangoproject.com/ticket/29999#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.33757eb460ec905db242556fa9f3fb3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
