First draft of a markdown IGN Sample report.

Attempting to turn [this bad boy](https://docs.google.com/a/scilifelab.se/document/d/1Sk10DZ4OFM4ikpjQMCqHBsryt8sWyDri0MpjkT6VMxI/edit#) into markdown.

Had to make a big compromise - HTML tables. Markdown tables have to have a horizontal header which isn't compatible with the output that we want. We also can't have nested Markdown tables to achieve the 2-column table layout.

Inserting raw HTML into the markdown template seems like an ok compromise to make though - we have complete control over the appearance and the code doesn't get _too_ messy. Everything else is still nice and easy to read / edit.

I looked into using RST as we currently do, but as far as I can see whilst being more powerful, it seems to suffer from many of the same limitations as described above.

Better solutions welcome! :)
Hand written by me, yeah. Once I get the PDF rendering it properly I'll swap out the static content with variable names. It won't look quite like the GitHub rendering in the PDF, I'll write a bunch of custom styling to get it to look like the sample report all being well. Does that answer your question?