Recently I was working on some documentation for a project and naturally I felt I would use Markdown for the job. It’s pretty standard amongst developers and used by GitHub and many others.

Also since I’ve been using hugo these days to generate static pages for my web content (like this one!), I use Markdown more and more.

Why Markdown?

Unfortunately our documentation platform only supports a WYSIWYG editor - ie. a ‘What You See Is What You Get’, Word-like experience with its pros and cons.

Let’s see first why you might want to use Markdown instead of your most likely fancier (web) editor…