docs: customizing header/footer templates
This commit is contained in:
parent
1ee9d7dd52
commit
f31a2f414a
1 changed files with 13 additions and 1 deletions
|
@ -99,4 +99,16 @@ There are three settings you can play with to control that:
|
||||||
# Which field to use in the URL, may also be for example "pk" to use the
|
# Which field to use in the URL, may also be for example "pk" to use the
|
||||||
# primary key and not expose the username (which may be private or may change too
|
# primary key and not expose the username (which may be private or may change too
|
||||||
# often for URL persistance)
|
# often for URL persistance)
|
||||||
USER_URL_FIELD = "username"
|
USER_URL_FIELD = "username"
|
||||||
|
|
||||||
|
|
||||||
|
## Custom header and/or footer scripts
|
||||||
|
|
||||||
|
You can populate the content of you own `umap/header.html` and `umap/footer.html`
|
||||||
|
templates with `<script>` elements, it might be useful for instance
|
||||||
|
for analytics (footer) or bug reporting like Sentry (header).
|
||||||
|
|
||||||
|
By default, these files are empty.
|
||||||
|
You must define you own paths for extra templates following
|
||||||
|
[Django’s documentation for this particular setting](https://docs.djangoproject.com/en/4.2/ref/settings/#templates).
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue