This is cool, but a lot of it is about bash programming, and it also heavily ties you to PDF output. IMO no real Markdown based authoring workflow is workable w

This is cool, but a lot of it is about bash programming, and it also heavily ties you to PDF output. IMO no real Markdown based authoring workflow is workable without a preprocessor. I've used many, from GCC's to several home written ones, but I recently started porting my whole authoring workflow for technical documentation to PP (http://cdsoft.fr/pp http://cdsoft.fr/pp). It gives you integrated diagrams with ditaa and several similar packages, and most importantly fills the gap that pandoc leaves wrt composing documents from fragments. Just treating all input files as one continuous input document just doesn't cut it for anything more than simple README's. Either way, it's great to see how far text-based authoring workflows have come over the last 10 years. At some point Docbook had great promise but XSL is just too hard, and not even that powerful after you managed to grok it, so you still needed to cobble together a bunch of functionality on top of it.