The markdown_gitbook format currently generates a SUMMARY.md table of contents file for publication via GitBook or mdBook, which makes it easy to import the generated Markdown output and spin up a site without much (or any) post-processing.
Various other Markdown publishing systems and static site generators each have their own file formats for defining the publication hierarchy.
Extensible ToC configuration
While this plug-in can't possibly anticipate all of the possible format combinations, I'm wondering if there would be a way to make this part of the process configurable or extensible, so that people could either change a series of options to generate a different ToC format, or develop a separate plug-in that overrides the process that runs for SUMMARY.md and generate a different file format from the map hierarchy.
We could then either document how to configure a different format with an example, or create a sample plug-in that generates a different ToC format.
The
markdown_gitbookformat currently generates aSUMMARY.mdtable of contents file for publication via GitBook or mdBook, which makes it easy to import the generated Markdown output and spin up a site without much (or any) post-processing.Various other Markdown publishing systems and static site generators each have their own file formats for defining the publication hierarchy.
Extensible ToC configuration
While this plug-in can't possibly anticipate all of the possible format combinations, I'm wondering if there would be a way to make this part of the process configurable or extensible, so that people could either change a series of options to generate a different ToC format, or develop a separate plug-in that overrides the process that runs for
SUMMARY.mdand generate a different file format from the map hierarchy.We could then either document how to configure a different format with an example, or create a sample plug-in that generates a different ToC format.
Examples
_meta.jsonnavbar items