#! blaze sh
The Testable Documentation Manifesto
One of the problems with tech documentation (api, installation instructions etc) is that they get stale. APIs change, software and plugins alter their interface and commands, and websites go away.
To solve this, I propose we write our documentation in a way that can be executed, or verified.
Luckily, I wrote
blaze to execute codeblocks inside of markdown, which means that with a little help from a few common unix tools, we can solve this problem.