A level-one header ================== A level-two header ------------------ Paragraphs are separated by a blank line. 2nd paragraph. *Italic*, **bold**, and `monospace`. Lists ===== Bullet lists ------------ A bulleted list item begins with a bullet (*, +, or -): * first item * second item * another item **Pandoc Manpage**: > The bullets need not be flush with the left margin; they may be indented one, > two, or three spaces. The bullet must be followed by whitespace. Ordered lists ------------- Here's a numbered list: 1. first item 2. second item 3. third item **Pandoc Manpage**: > In standard markdown, enumerators are decimal numbers followed by a period and > a space. The numbers themselves are ignored. Unlike standard markdown, Pandoc > allows ordered list items to be marked with uppercase and lowercase letters and > roman numerals, in addition to arabic numerals. Nested lists ------------ Now a nested list: 1. First, get these ingredients: * carrots * celery * lentils 2. Boil some water. 3. Dump everything in the pot and stir :-) Definition lists ---------------- Term 1 : Definition 1 Term 2 with *inline markup* : Definition 2 Code ==== Indented code blocks -------------------- Here's a code sample (indented four spaces): zipWith :: (a -> b -> c) -> [a] -> [b] -> [c] Fenced code blocks ------------------ **Pandoc Manpage**: > Fenced code blocks begin with a row of three or more tildes (~) or backticks > (`) and end with a row of tildes or backticks that must be at least as long > as the starting row. ~~~ zipWith :: (a -> b -> c) -> [a] -> [b] -> [c] ~~~ Optionally, you may attach attributes to the code block using this syntax: ~~~ {.haskell .numberLines startFrom="100"} zipWith :: (a -> b -> c) -> [a] -> [b] -> [c] ~~~ A shortcut form can also be used for specifying the language of the code block: ```haskell zipWith :: (a -> b -> c) -> [a] -> [b] -> [c] ``` Links, footnotes and images =========================== Here's a link to [a website](http://foo.bar), to a [local doc](local-doc.html), and to a [section heading in the current doc](#an-h2-header). Here's a footnote^[Footnote text goes here.]. This is an image:  This is an *inline* image: \ (notice the backslash) Math ==== Inline math equations go in like so: $h(n) \le c(n,a,m) + h(m)$. Display math should get its own line and be put in in double-dollarsigns: $$a_j = \left\{ \begin{array}{lll} 1 & \text{ falls } & w_{0,j} + a_1 w_{1,j} + a_2 w_{2,j} + ... + a_n w_{n,j} \ge 0\\ 0 & \text{ falls } & w_{0,j} + a_1 w_{1,j} + a_2 w_{2,j} + ... + a_n w_{n,j} < 0 \end{array} \right.$$ **Pandoc Manpage**: > Anything between two `$` characters will be treated as TeX math. The opening > `$` must have a character immediately to its right, while the closing `$` > must have a character immediately to its left. LaTeX Macros ============ **Pandoc Manpage**: > For output formats other than LaTeX, pandoc will parse LaTeX `\newcommand` > and `\renewcommand` definitions and apply the resulting macros to all > LaTeX math. > > So, for example, the following will work in all output formats, not just LaTeX: > > \newcommand{\tuple}[1]{\langle #1 \rangle} > > $\tuple{a, b, c}$ > > In LaTeX output, the `\newcommand` definition will simply be passed unchanged > to the output.