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
Better Plugins: Hooks #1414
Comments
🆒 Great idea. I'm all sorts of for this. |
🆒 👍 🎉 On Mon, Aug 12, 2013 at 7:29 AM, Ben Balter notifications@github.comwrote:
|
Like post-receive hooks? That's a great idea! |
Conceptually, yes! Upon running Jekyll with plugins, plugins could specify a block or something to execute right before or after something happens. |
Where would those live ideally? At some API endpoint? |
It'd besomething like |
+1 |
I think the only thing that's worrisome here is the order in which the plugins are allowed access to the content. We've had this trouble with other CMSs: plugin All of that said, we should totally still do this, since it offers a very elegant approach to content manipulation. |
The order is problematic, yes, but it's way better than the problems with the plugin order in the current monkey patching approach. |
Damn straight. 👍 |
In the works, closing this. |
One of the sticking points for plugins is all the monkey-patching craziness necessary to do even the simplest of actions.
One idea I'd like to toss around is this idea of hooks. In a similar manner to rails, it would be easy to call methods before and after various actions. I'd propose the following:
What is the general consensus around hooks?
//cc @mattr- @benbalter @qrush @mojombo
The text was updated successfully, but these errors were encountered: