tldr; How does one properly add individual syntax extensions to jekyll/kramdown?
I think this means refactoring the plugin to be more converter-like, but I think a converter plugin would then be responsible for rendering the entire markdown file, which I don’t want. I just want to add one new piece of syntax to parse.
I found this implementation, which if I understand correctly, is subclassing Jekyll’s
Convertible module and calling its own transforms for [[wikilinks]] just before calling the regular
transform method. It sounds like just what I want.
So, I would like to refactor my plugin to match this implementation, but I can’t seem to get the example I found to hook into Jekyll. I run the usual
bundle exec jekyll serve --trace and the plugin code is never run. It’s an older example (8 years old), but after perusing the existing
transform method, it seems to check out – e.g. it’s overriding modules that still exist. So I don’t understand why the example isn’t running for me.
Any help is appreciated, as well as input about manner of implementation. I would like this to be a robust plugin that adheres to jekyll/kramdown standards and has intuitive usage that meshes with the rest of the framework.