jquery/web-base-template — comment on commit 4dc13a551a32a08ef2ea38246972df988bdeb2c5
File:  line 0
By rdworth:

We don't have everything in one file, we have everything in one of two files. The main style.css should have styles that are needed for all sites or more than one site (that is, as soon as two sites need the same css, they share it by having it in that file, which means all sites have it). And the other file should have styles that are intended only for that one site.

As far as "begs for problems along the way" these are problems we will have and need to solve but they are not solved by having a bunch of separate files and too many http requests (nor a complex build step that generates a unique stylesheet for each site, meaning again too many http requests and less caching benefit). The solution is to have a single file that is well organized into styles that can be used across multiple sites. Yes, that does take a bit more effort, but it accomplishes what is truly needed. When we come up with a piece of design, if it has potential to be used on sites other than the site or type of site for which it was originally developed, neither the classname or the filename should stand in the way of sharing that style without duplication. This inset-link is a good example of this, and is exactly the reason I found this commit and commented on it. I went to use it on the plugins site but wasn't able to because it's tied to the comments-link-top class and is inside a file called blog.css. Neither work for the use case, but the inset-link feature (as a design feature) should not be so limited, as there's nothing blog specific or comment specific per se about it.

It looks great, btw, which is why I'm so anxious to be able to use it on the plugins site :D