Hugo --filter script.sh ? running the markdown files through a filter before processing

I don’t code in Go, and i’m just learning the basics of Hugo, but this comparison point of how config options are made use of with GoldMark seems helpful:

It seems like it should be fairly straightforward for one of the core dev team to add in two pandoc options:

  • executable
  • options

Of note, the executable option wouldn’t be tied to pandoc really. So it might actually work to make any parser engine work as the parser, especially if additional config can passed as an argument (perhaps as JSON?). That might be valuable, in that it could allow inheritance of config properties…

But just doing this for pandoc would be quite powerful and helpful.