git.iko.soy/typeable/pandoc
on master help sign in
Documented fact that you can put YAML metadata in a separate file.

See #1412.

commitca159de30a2b3653ce668799a168993b5a2ca76d authorJohn MacFarlane <jgm@berkeley.edu> dateThu 10 Jul 2014, 13:49 (12 years ago) parent6637806
1 file changed+8−1
README+8−1
README+8−1
@@ -1842,7 +1842,14 @@ A YAML metadata block is a valid YAML object, delimited by a line of three
18421842hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots
18431843(`...`) at the bottom. A YAML metadata block may occur anywhere in the
18441844document, 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+`...`.)
18461853
18471854Metadata will be taken from the fields of the YAML object and added to any
18481855existing document metadata. Metadata can contain lists and objects (nested