Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Basic extension support [patch] #100
Based on the 240 forks Jekyll has, people are finding the base code slightly less than what they need. For instance, I have 3 custom liquid filters that are custom enough to not be worth even trying to merge into the mainline code.
That said, I hate that I need to maintain a branch if I want to pick up any new code - I'd rather keep my patches in my blog itself, and just have Jekyll load them when I build.
So, I added loading jekyll customizations from a directory in the site (anything matching _lib/*.rb). Based on qrush's comments in some other tickets, github would need to add --no-extensions when processing github pages to remain "safe" from injected code. Branch pushed to http://github.com/jamie/jekyll at master.
It's a very small change, just meant to let me get some custom liquid filters in. Config option, defaults, and features included.
May I recommend this quick fix while you are waiting for this to be accepted:
you wrap the jekyll script to import the liquid filters yourself so you can still use default jekyll gem.