Our scenario is the following:
We're building a portal software (www.discoverize.com
). Without any custom configuration, a new portal has our
theme activated. Once we build a custom theme for a certain portal, we want to diverge from the defaults here and there - e.g. replace default images from the
theme with specialized images for the concrete portal. Everything else should just fall back to using the
Now, to reference static resources in a clean way I'd just use some unified, theme-agnostic url for them, e.g. /styles/img/favicon.ico instead of /themes/neutral/styles/img/favicon.ico. This is especially important inside CSS files as there I can't modify the
generated link the way that would be possible in some razor view, e.g. layout.cshtml.
Just now while writing this I remember that there is the HTML
tag but doing a quick search for it pointed me at
this stackoverflow question
where the OP in his own answer points out the tricky problems this may produce. So I'd be rather unwilling to use the
although it'd seem like a perfect fit at first (especially, for the urls embedded in css files).
What other approach would you suggest to satisfy these requirements?