Where does Markdown fall short

Why do developers not question the suitability of Markdown in a space where Web content is componentised?

Markdown is Good Enough, ish

</p> <h2>Accessibility Limitations</h2> <p><a href="markdown.html">Markdown</a> provides a satisfactory solution for simple developer documentation, note-taking and text-based blogging served through static site generators. Being plain-text it integrates well with source-control tooling and generating diffs. This closeness-to-the-wire limits non-technical users from fully engaging in the format without additional supportive tooling. This can lead to a disparity between documentation for developers and documentation (using a Wiki tool or traditional Office-based formats) by non-technical people.</p> <h2>Next Direction</h2> <p>Treat content as data using Structured Content</p> <section id="backlinks"> <h3>Links here</h3> <ul> <li> <a href="./top-of-my-mind.html"> <h4>Top of my Mind</h4> <p>I want to learn more about Structured Content, particularly after thinking through the implications of Where does Markdown fall short.</p> </a> </li> </ul> </section>