Custom server-side scripting

[jannis-baum]

will allow e.g.

• adding markdown-it plugins Vivify doesn't use
• pre-processing file contents before passing them through Vivify's parser
• post-processing file contents after passing them through Vivify's parser

could also consider allowing to inject at arbitrary points in Vivify's parser

context: I want to use it to render some LaTeX stuff that I don't want to upstream to Vivify, e.g. for custom management of citations & files that will produce PDFs through Pandoc & this will also allow for customization like #198

[jannis-baum]

The above stuff can (probably?) be solved by offering a custom callback and passing the markdown-it into it, that way you can do everything with custom or installed plugins.

Another thing that would be great is to do the same callback thing with the router as well. That could allow adding new end points the client can call. Example:

• custom markdown-it plugin adds a button for clicking on references
• button triggers custom end point that runs something to open that reference

So maybe

• offer two different types of server scripts:
  • one for parsers that export a default function that gets the mdit
  • one for routers that export a default function that gets the router
• these could be either
  • as two distinct config options
  • as files with .router.js or .parser.js suffixes

[jannis-baum]

Could also consider making a "plugin" infrastructure for this

EDIT: I guess we already have something close enough to plugins without calling it that, you can e.g. have a repo as a subrepo of your dotfiles and glob include styles and scripts in Vivify's config to install the plugin

EDIT2: Although we could make something like runtimepath in (N)vim and use default directories for styles, client scripts & server scripts

[jannis-baum]

#262 (comment)