>>/20794/
So this is "interesting". Since you asked, I was about to say that's probably the best solution and go ahead because even though the file will end up >1MB, most browsers will cache it, and those that don't still only need to download a tiny fraction of that (<100K) since the css transfer should be compressed. But then I try to verify that and see that while the "static" css are in fact sent compressed, the custom.css is not. That should be fixed in the board software.
So >1MB css each visit is not nice, but I personally know how to override it locally and since I only post once ina blue moon is really up to you to decide I just thought about mentioning it