Allow configurable `head` items for CSS or JS files
Currently it is necessary to overwrite the
core/_head.html template (and configure a priority template directory for its path) in order to add resources to the
head section of the emitted HTML content.
This is relevant for embedding additional CSS or JS assets.
Instead we should allow the configuration (in
grouprise.settings) of such resources.
I can imagine two approaches:
- A) Add
SITE_ASSETS_CSSas lists of URLs referring to such resources (to be part of the
- B) Add
GROUPRISEsettings dictionary. This list would contain raw HTML content (e.g.
<link rel="stylesheet" href="/stadt/css/foo.css">).
(A) would look nicer, but may require additional work for each additional type of meta data (anything that is allowed in
(B) looks a bit more raw, but gives more control over the
What do you think?