allow for markdown / HTML (or mdjs) authoring for blog posts

[thescientist13]

Something in Greenwood should allow it so blog posts can be authored in true markdown, not a HTML file wrapped in ``` render blocks, ex.

---
template: 'blog'
---
  
```render
<app-blog-post 
  title='Git Explorer' 
  date='04.07.2020' 
  image="/assets/blog-post-images/git.png">
        
  <div>

    <p>Made this a little while ago but felt it would be fun to share, called <a href="https://github.com/thescientist13/git-explorer" target="_blank" rel="noopener" @onclick="captureOutboundLink('https://github.com/thescientist13/git-explorer'); return false;"><b>Git Explorer</b></a>.  It is a NodeJS package you can install from NPM that will provide a nice browser based comparison tool for any <code>git</code> repo on your local machine.</p>

    <img src="https://raw.githubusercontent.com/thescientist13/git-explorer/master/git-explorer.png" alt="Project Screemnshot">
    
    <p>Checkout the <i>README.md</i> for more info and feel free to submit an issue if you see a bug or would like to request a feature. 👋</p>
          
  </div>
</app-blog-post>
```

[thescientist13]

In latest Greenwood now we don't need ```

but it still requires certain formatting around the line breaks, ex. 2

---
template: 'blog'
title: 'Teaching An Old Dog New Tricks!'
---

<app-blog-post
  title='Teaching An Old Dog New Tricks!' 
  date='03.30.2017' 
  image="/assets/blog-post-images/angular-shield.jpg">

  <div>
    <p>Since not all existing AngularJS (1.x) projects can jump into using Angular (2+) and <i>ng-upgrade</i> may not be a feasible option for some, I created <a href="https://github.com/thegreenhouseio/angularjs-webpack-seed" target="_blank" rel="noopener" onclick="getOutboundLink('https://github.com/thegreenhouseio/angularjs-webpack-seed');">a seed repo in GitHub to demonstrate AngularJS working with webpack and ES2015+ syntax.</a></p>
    <p>To me, ES2015+ syntax, in particular the introduction of modules (<i>import / export</i>) has ushered in a new era of writing JavaScript applications, including our good friend AngularJS.</p>       
    <p>By adopting ES2015+ syntax and following meaningful styleguide conventions like John Papa&apos;s, these effort can really go a long way to improving the readability and organization of an existing AngularJS app.  Plus, if you can slowly migrate through the releases of AngularJS &gt; 1.5, you can set yourself up for a migration path to Angular now.</p>
    <p>This seed is not meant to be comprehensive, but just as a way to show that any existing AngularJS app can benefit from an ES2015+ upgrade, backed by webpack.</p>
    <p>Hope to hear your thoughts and feedback!</p>
  </div>
  
</app-blog-post>

Or else the content breaks and the IDE also stops showing code formatting