I would like to put up and ask for review of https://github.com/jekyll/jekyll-assets so that all Github users can get the full arm of assets on their Github Pages sites.

With the next version we also plan to implement Jekyll safety to allow and disallow certain plugins if Github wishes however... at this time we already fall inline with Jekyll and assure that every given asset lands within Jekyll's own root.

Any update on this?

users can get the full arm of assets on their Github Pages sites.

@envygeeks thanks for following up. Can you explain a bit more about what you mean by that? What would the plugin allow you to do that you can't do now? Who's the target user? What's the target use case? Would love to learn more.

Feels like an automated response @benbalter 😉. Jekyll as it stands is a very basic version of what Jekyll Assets can do and could never match what Jekyll Assets could do unless it took over and started doing it. Not only do we support SCSS/SASS better, but we support CofeeScript better, we support ES6,ES7, proper asset management, minimizing, optimizing, and dozens of other languages (except ERB -- for what should be obvious reasons.) Think Rails assets without Rails, and with more constraining.

Users want Jekyll Assets. This request isn't for me, I get dozens of emails a week, have dozens of tickets on my tracker (and Jekyll's tracker -- along with support for it from other Github Staff --) I host my own Jekyll, it's for the users who keep asking me about it and asking me to see if I can get it included.

The target user is anybody who wants real assets, or who wants to do real things with assets through Github pages without needing to pre-process locally and then upload that source to Github. I know more people who currently use Jekyll Assets or NodeJS stuff to preprocess before uploading to Github than I don't now days. Jekyll's built in SCSS is great for a basic site, but what happens if you wish to host a real site on Github? You've to pre-process, and that's pretty bad flow, when we could try to get Jekyll Assets embedded into Github Pages and increase it's power. Want ES6/7 + React + Redux without needing to pre-process locally or without having to use NodeJS? Now you can.

The cases are obvious, or should be, Jekyll Assets is the big brother to what Jekyll currently does, I'll admit it should be an optional addon, in that it shouldn't be loaded by default unless the user adds it to their plugins, but I think it should be an option. Where Jekyll wants CoffeeScript, I use ES7, where Jekyll wants SCSS at it's most basic, I want the full-arm of SASS with full support for importing optional external dependencies like bootstrap.

Users ask for Autoprefixing of their assets? Jekyll Assets got's your back, we already support it. Want bootstrap without having to maintain a local copy? We got your back, it's a plugin. Want ES6? It's supported. Want ES7? It's supported, want LESS? We got you covered. Want Jekyll on Github to process your assets and then host those assets on your own CDN? Got you covered. Want to process your assets with liquid so you have fluid assets? No worries, it's supported. Want to resize or adjust your images? We got that handled too.