4 ms·
I'm quite sure that facebook would follow a lot of what is being advocated in here, but then css variables get expanded etc to give them 6498 variations. For t
by 5h 15y ago
I'm quite sure that facebook would follow a lot of what is being advocated in here, but then css variables get expanded etc to give them 6498 variations.
For the past 5 years or so I've had an average an average of 8 base css files for most projects, normally along
the lines of page layout / typography / individual elements in different contexts / interactive elements & their mobile equivalents in separate files then a separate file for each ~type~ of content object within a page, sass gets expanded, then they get minified & cached as one file. Along with saving a hash of their internal paths to prevent the majority of cache misses, I've found this works well (for javascript also) & other than hand-tweaking a couple of homepages or high traffic landing pages haven't had to do much else.
edit: to be clear, the article is great advice but would have you end up with a monolithic common.css, don't do that, there are better alternatives