getpelican/pelican — pull request #488 by dmdm (2012-08-27 22:57:56+00:00)
Title: Patch to allow relative ASSET_URL

Previously, webassets' ASSET_URL always was absolute.
This patch allows a relative ASSET_URL, depending on Pelican's
RELATIVE_URLS setting.

Hint for templates:
-------------------
Current version of webassets seem to remove any relative
paths at the beginning of the URL. So, if RELATIVE_URLS
is on, ASSET_URL will start with 'theme/', regardless if we
set assets_url here to './theme/' or to 'theme/'.
XXX However, this breaks the ASSET_URL if user navigates to
a sub-URL, e.g. if he clicks on a category. To workaround this
issue, I use

instead of

Maybe this hint is worth to be included in the documentation.
I have it also written as comments in the source.