Say Yes to Markdown, No to MS Word
I&#x27;ve spent the bulk of my career on content-driven apps, ranging from basic CMS systems to platforms that manage workflow of large, complex, legal documents. And I can tell you that while Markdown works for basic formatting of short documents, it falls short when you work with people whose entire lives revolve around long documents with complex formatting. (Attorneys, policy writers, etc.) A UX that exposes markdown to that crowd just isn&#x27;t widely accepted. And that is before we even get into actual features like TOCs, headers, pagination, margin control, nested tables, etc.<p>Now, the benefits of Markdown listed in the article are all true -- but also only loosely tied to the UX of the actual document authors and editors. If Markdown supports your formatting needs, sure, it is a good storage syntax for your content, fine. But don&#x27;t make attorneys, policy writers, etc., use it. I&#x27;m not saying MS Word is the only answer either, but I highly recommend that people find&#x2F;modify&#x2F;create a more robust editor for your authors.