rdrewniak
commented
6 years ago What might be an interesting way to approach this is to make the Sass compiling and javascript concatenation optional.
If I had the ability to silo my stylesheets by compiling my Sass files into multiple documents that are devoted to elements or sections that I define as self-contained entities. For example, when compiling my Sass, my Foundation 6 styles could be separated into their unique entities, like a xy-grid.css, menu.css, dropdown-menu.css file.
I'd love to see the option (which I could configure in the initial environment development) to set up multiple Sass compilers that result in a larger number of smaller CSS files.
Then, if it's optional, the community could have the best of both worlds: keeping the same system that those who host their websites in shared hosting environments that don't yet support HTTP 2 (cough looking at you, GoDaddy) need, and allowing the modern web hosting providers like SiteGround to run at optimal efficiency.
Hello! Not really an issue, but more a thinking... With now HTTP 2 spreading everywhere, the concept of loading everything one time seems to fade away... I already used some "is_single('aaa') or any other page type detection in wordpress to load just what the user need to see the page (javascript, not the css)... What do you guys think about it? Interesting reading: http2-Best-request-no-request Thanks!