Add support for Pelican templates

[remarkjs]

Add support for Pelican templates

[wooorm]

You could try something like this through a syntax extension indeed, for short codes. However, it’s impossible to totally support real template languages, as they could generate other markdown constructs.

For example, say we have a fictional template language where in {foo}[link](url) the {foo} part would expand to !, we’d now have an image instead of a link.

[ChristianMurphy]

Similar to remarkjs/remark-lint#202
This would be a good parser extension for remark itself.

It may be possible to reuse https://github.com/djm/remark-shortcodes configured to use {} are the markers.
Then add a follow up plugin that can replace the shortcode with the variable/path as Pelican would resolve it.

[wooorm]

Closing this as it’s not an issue that needs to be solved here!