btaens

I suppose a constant could be defined that reads a Config parameter, but that seems a bit hacky, and it might not be desirable to litter the namespace with constants...

That would actually make more sense. I was actually about to ask what delimeter you prefer. Sure thing.

Might make sense, perhaps even have the possibility to replace references in stylesheets at compile time? That might require some advanced parsing though, really just having the possibility to simply...

Changing css references would be very useful, but simple symlinking is already really good. Rewriting paths might get tricky. There are a lot of ways to reference assets. Though yes,...

Actually, I do see a CSSUrlRewrite pull request from back in 2013. Did that not work out? What happened?

Alright, I've been thinking about this CSS URL rewriting business, looking around the code. Theoretically, it could be a seperate Filter. The user would simply provide a target directory for...

There's also the possible problem of absolute paths being provided in a css file (like `/img/logo.png`), as we don't know what it constitutes as the root folder.

Yeah, that's the other option. If we're working with a manifest though, the question again is, do we just ask for a file path, and then try to replace in...

A simple solution might just be to require relative paths. Absolute ones are bad practice anyway, and vendor libraries don't _much_ do it. So maybe we just don't touch absolute...

Could we assume the provided paths are the root path for a file in question? That would basically solve it, although you'd have to provide a path to each vendor....