Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic extension support [patch] #100

jamie opened this Issue Nov 29, 2009 · 3 comments


None yet
5 participants
Copy link

jamie commented Nov 29, 2009

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 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.

Suggestions welcome.


This comment has been minimized.

Copy link

bentomas commented Jan 6, 2010

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.


This comment has been minimized.

Copy link

jodosha commented Jan 16, 2010


This comment has been minimized.

Copy link

mojombo commented Jun 19, 2010

The latest on master now has Plugin support. Look at lib/jekyll/converters for examples of how they're done. Also, any *.rb files in a _plugins directory will be loaded so that you can create custom plugins of your own.

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.