---
title: Why, how and whats of Markuw
subtitle: Mark[up|down] the UNIX way
author: Jeremy Theler
fontsize: 11pt
lang: en
numbersections: true
formats: html tex pdf
template: light
...

# Why

Because the generation of documentation is completely creepy using traditional (i.e. word processors).

# How

Write in Markdown. Track with Git. Read in

 * HTML (responsive)
 * PDF (through XeTeX)
 * $\dots$ (whatever Pandoc converts to)
 
# What

## Markdown

Focus on the content. Use headers, lists, tables (through Pandoc extension), etc. And of course beautiful math

$$
\int_{a}^{b} \frac{dF}{dx}\,dx = F(b)-F(b)
$$

## Git

Track changes. Collaborate. Get the hash of the latest commit into the resulting document. And an\ $\varepsilon$ if there are uncommitted changes.

## Advaced tweaks

Actually M4 macros can be expanded, Bash hooks can be executed, Pandoc filters can be used and templates can be fully customized. The UNIX way.

