I agree totally. I have used php to compile and minify before this and never had to deal with so much waiting. And sage takes up more space then the entire wordpress site. It feels like towing a bicycle with a tractor. I would suppose there is a way to slim down the processing and dependencies but have not had the time to look into it.
ā¦except .svgās and .mp4āsā¦ so how the hell do you reference those from the css? (not a rhetorical question, I desperately need to know)!
svgās shouldnāt be ignored, at least not in the latest versions of Sage.
For mp4ās, yes itās true thatās not handled by the gulpfile/asset builder. However, why couldnāt you reference the video directly from the assets directory?
At the moment the types of files to pass arenāt editable via manifest.json
, so best option would be to reference the file outside of dist
I just wasnāt sure if doing ../../assets/foo/bar.biz
was ābest practiceā. Iām introducing my team to Sage and itās a little wonky to say "use ../foo/bar.biz
for everything, except not these things, if you know what I mean
Not sure why my SVGās arenāt appearing in dist/images
, Iām using the latest Sageā¦ My gulpfile is the same as the one in the main branch of the repoā¦ must be aliens.
UPDATE: SVG gulp process working now, must have been a bug with the SVG file I was testing with. Cheers.
Sure, I can appreciate that. Video is a rather edge case though, so it wasnāt really thought of to put it into the asset builder. Especially since the node modules that are installed already equal quite a hefty download with all the image optimization modules.
You could potentially duplicate the āfontsā task in the gulp file and have it copy a video
folder. That would allow you to keep the same workflow as the rest of the assets.
You rock, I owe you a beverage of your choice. Thanks for taking the time to respond!