Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Decouple CoffeeScript and Sass gems. #2362
Strong coupling requires a huge investment by users in terms of
To install either of these gems, run
Jekyll shall not be bloatware.
referenced this pull request
May 9, 2014
Because it's adding bloat. If I have NodeJS installed, I don't want to spend the time installing yet another gem I don't need or want. It's really about bloat. I'd rather decouple in the manner proposed because it introduces a very, very light lift for those that want to use Sass & CoffeeScript, and removes the bloat for those who don't.
The question is, do you provide this documentation on the Jekyll page, on the Jekyll-(Sass/Coffeescript) page or both? Clear and concise is great but the hardest part is deciding where to place all this information because placing it on the wrong spot is just as bad as not documenting it sometimes.
That said, I think this is an occasion where I would probably deprecate the feature in a minor bump and then remove it in a major bump, add a warning (with a switch to disable it of course) letting them know that the gems will be decoupled come Jekyll v2.* and that they should ensure that they have them added to their Gemfile if they use them and wish them to remain on by default.
The current Jekyll guide will result in a non-functional Jekyll installation, so it seems like the extra step would need to be mentioned there.