Add an endpoint to the ZMarkdown server that takes a manifest (ie. file describing the full architecture of a content, see below) and renders it as HTML, LaTeX or EPUB.
What's a manifest, anyway?
This gist shows an example of a manifest as provided by zds-site (manifest-raw.json) and the corresponding manifest required by ZMarkdown (manifest-arduino.json). Basically, it describes a content and it's internal structure.
Currently, zds-site sends every extract to ZMarkdown, and assembles it itself, in an unparallelized manner, leading to a slow rendering process. The goal is to speed it up, and also to assemble VFiles correctly (that is, error messages, statistics, etc) to get a coherent result.
Add an endpoint to the ZMarkdown server that takes a manifest (ie. file describing the full architecture of a content, see below) and renders it as HTML, LaTeX or EPUB.
What's a manifest, anyway?
This gist shows an example of a manifest as provided by
zds-site(manifest-raw.json) and the corresponding manifest required by ZMarkdown (manifest-arduino.json). Basically, it describes a content and it's internal structure.Currently,
zds-sitesends every extract to ZMarkdown, and assembles it itself, in an unparallelized manner, leading to a slow rendering process. The goal is to speed it up, and also to assemble VFiles correctly (that is, error messages, statistics, etc) to get a coherent result.