git.iko.soy/typeable/pandoc
on master help sign in
Documented fact that you can put YAML metadata in a separate file.
ca159deJohn MacFarlane
README+8−1
@@ -1842,7 +1842,14 @@ A YAML metadata block is a valid YAML object, delimited by a line of three
1842hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots
1842hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots
1843(`...`) at the bottom. A YAML metadata block may occur anywhere in the
1843(`...`) at the bottom. A YAML metadata block may occur anywhere in the
1844document, but if it is not at the beginning, it must be preceded by a blank
1844document, but if it is not at the beginning, it must be preceded by a blank
1845−line.
1845+line. (Note that, because of the way pandoc concatenates input files when
1846+several are provided, you may also keep the metadata in a separate YAML file
1847+and pass it to pandoc as an argument, along with your markdown files:
1848+
1849+ pandoc chap1.md chap2.md chap3.md metadata.yaml -s -o book.html
1850+
1851+Just be sure that the YAML file begins with `---` and ends with `---` or
1852+`...`.)
1846
1853
1847Metadata will be taken from the fields of the YAML object and added to any
1854Metadata will be taken from the fields of the YAML object and added to any
1848existing document metadata. Metadata can contain lists and objects (nested
1855existing document metadata. Metadata can contain lists and objects (nested