Markdown vs HTML

Markdown converts to HTML. It’s designed to do that. But it’s drastically simpler in form than HTML. What if we could replace HTML altogether?
Right now, Markdown is built to support HTML directly. So to support Markdown is to support all of HTML as well. What if we just remove the HTML support and build Markdown as the language the browser understands natively?
Benefits:

• Markdown is far easier to read than HTML.
• It’s far faster to parse, no open/close tags.
• Smaller file size; since there are no open/close tags.

Tying in with the proposal to code in English, Markdown would provide a familiar, written form to compliment the English language.

CSS and JavaScript

Both CSS and JavaScript can be included using code blocks.

  body { background: white;}

  console.log('This will be executed.');

Further Consideration

Various projects already exist to simplify use of Markdown either within HTML or by using an HTML page for boilerplate and Markdown file(s) for content.
Consider this: https://news.ycombinator.com/item?id=18154825
GitDown was designed to do roughly the same thing. There are others as well. But like GitDown, Markdown page simplifies everything to the point that forking the repo on GitHub and then editing the relevant Markdown file(s) results in a ready-made web page.