And here I am an hour before publish time, with a take being bashed out in real time.
My take is this: Please, please, please, please, please, please, please, please stop pretending that Markdown is a developer format first. It’s not. You’re deluding yourselves otherwise.
Yes, it might be inspired by programmer-style thinking. Yes, developers have found lots of reasons to make use of Markdown as a way to implement some structure into the content they create. Yes, whole genres of content-management platforms have been built around the rise of Markdown. But writers and editors, who actually do a lot of the work in the format, get lost in a discussion when it’s being led by someone who works for a company with the tagline Content is Data
(The hell it is. Data implies a methodical nature to the process of creation. It implies that creative output should be treated in the same context as programming. And you know what? That is the wrong order of things. Data serves content. If I was looking for a CMS and I saw that “Content is Data” tagline, I would close the tab.)
The thing is, whether the use case is documentation, or you have a folder full of files that you bash out with a quickness and intensity that avoids all the extra crap that comes with a word processor, it’s important to keep in mind that this all starts with the content, and the tools, and the way that people create things.