Statik needs a good plugin system

[thanethomson]

It's all good and well to be able to include custom template tags and filters, but there's some functionality (e.g. the Netlify deployment) that really should be provided by some kind of plugin.

The best plugin architecture would replace custom template tags and filters completely, and have the following properties:

1. Simple to install: e.g. statik plugin install https://github.com/path-to/plugin or statik plugin install some_plugin_name (for plugins whose packages are on PyPI).
2. Simple to remove: e.g. statik plugin uninstall https://github.com/path-to/plugin
3. Automatically detected by Statik.
4. Be able to provide custom template tags and filters.
5. Be easily testable.

[thanethomson]

Should consider refactoring Statik to use Cement as its underlying framework. Plugin functionality comes built-in.

[dennohpeter]

When is this happening @thanethomson ?

[dennohpeter]

we kinda need plugins now..

[thanethomson]

@dennohpeter - feel free to build one and submit a PR! 😁

[dennohpeter]

😁😁😁👋

[dennohpeter]

A plugin or the cement integration thing...?

[thanethomson]

A rebuild of Statik on top of Cement, since Cement comes with a plugin system.

I haven't had time to work on this in the past couple of months due to other pressures.

[dennohpeter]

ok got you 👍