Please provide a bunch of convenient YAML frontmatters to unleash the power of pandoc with the following keys:
page: a numerical value. The page-key will be used for the pandoc-plugin when merging a bunch of md-files within the current workspace. The pandoc-plugin can use the page-key to derive the sequence when merging multitple pages (e.g. "page 1" comes before "page 2"). The pandoc-plugin uses a file with page=0 as the cover of the book and a file with page=-1 as the backcover of the book. The page-key can also be called order or sequence, because its value is not really mapped to the real page number and only be used to derive the order of the merge process, for example: document1 with page=1 (consists of 3 DIN A4 pages) and document2 with page=2 (consists of 5 DIN A4 pages), then the overall real page number is 1*3 + 2*5 = 13 pages. The document2 starts at page 4 , because document1 fills the pages from 1 till 3 (n+1 = 3+1 = 4) and document2 fills the pages from 4 till 9.
title: a string value. The title will be used when generating a TOC (within a pdf, epub, etc.). By default it uses the name of the md-file. By default, the obsidian-pandoc should read the folder-structure of the current workspace to know how to generate the TOC, i.e. the sub-folder(s) represents sub-sections mapped in the TOC. In combination with thepage-key, an ordered TOC can be generated as the first site within the merged output (e.g. pdf, ebup). The pandoc-plugin can generate a TOC by default when a page-key is given.
Please provide a bunch of convenient YAML frontmatters to unleash the power of pandoc with the following keys:
page: a numerical value. Thepage-key will be used for the pandoc-plugin when merging a bunch of md-files within the current workspace. The pandoc-plugin can use thepage-key to derive the sequence when merging multitple pages (e.g. "page 1" comes before "page 2"). The pandoc-plugin uses a file withpage=0as the cover of the book and a file withpage=-1as the backcover of the book. Thepage-key can also be calledorderorsequence, because its value is not really mapped to the real page number and only be used to derive the order of the merge process, for example:document1withpage=1(consists of3DIN A4 pages) anddocument2withpage=2(consists of5DIN A4 pages), then the overall real page number is1*3 + 2*5 = 13pages. Thedocument2starts at page 4 , becausedocument1fills the pages from 1 till 3 (n+1 = 3+1 = 4) anddocument2fills the pages from 4 till 9.title: a string value. The title will be used when generating a TOC (within a pdf, epub, etc.). By default it uses the name of the md-file. By default, the obsidian-pandoc should read the folder-structure of the current workspace to know how to generate the TOC, i.e. the sub-folder(s) represents sub-sections mapped in the TOC. In combination with thepage-key, an ordered TOC can be generated as the first site within the merged output (e.g. pdf, ebup). The pandoc-plugin can generate a TOC by default when apage-key is given.For example: