Result:
This creates a new blank blocks.scss at top-level and blocks.css content is not imported into the compiled bootstrap/css/bootstrap.css file as expected.
Why is it creating the blank blocks.scss file and not just importing the contents of blocks.css into the compiled bootstrap.css file?
Hi @chitown,
Pinegrow uses LibSass as its processor. As of a version (or so) ago, supporting the import of .css files was deprecated. This was because of technical specifications in the original SASS language (lots of argument about this one!). A work-around to this (but you have to be careful) is to give the files a ‘.scss’ extension and then @import. The processor will treat these files as sass files and process them, so your files should be pretty plain css without variables and the like. Otherwise, you need to go with an outside processor where you can install an extension as workaround or use dart.
Cheers,
Bob
@RobM Interesting. Thanks for sharing. I thought I was doing something wrong, but it appears it is working as expected.
I guess I will have to reconsider my workflow and merge CSS files together another way. Always try to limit files loaded for page speed. Changing file extensions would not work with something like animate.css that has a lot of files to import.
You could copy your additional css to custom.scss and it will appear at the bottom of the bootstrap.css that’s the idea of the Pinegrow scss setup! With clear comments of course. So you end up with one dist (distribution) file bootstrap.css
…which segways nicely into my recent query post about Node etc…
as Id just got to exploring Bower, and now
GULP
Would it be worth some sort of TUTORIAL or such like exploring different sorts of Pro set ups?
Worded for both those Pros… and beginners to try it out?