npm-eslint-markdown VS marked

In our demo application, we're using highlight.js and Marked for markdown processing and syntax highlighting.

So I built a single-page viewer in one HTML file that reads the markdown directly. The whole site is one index.html plus the markdown files. You open the HTML in a browser, it fetches the markdown, renders it with marked, and you have a real navigable site.

marked.js for markdown rendering

it is trivially easy to create your own with libraries like this [0] (34k stars) or this one [1] (444 stars).

0: https://github.com/markedjs/marked

ADR-003 documented the choice of markdown-it over alternatives like marked, based on careful evaluation of edge cases and built-in features like URL linking.

Another option is to go with a purpose-built tool, like SlickPDF. I built slickpdf.com for the very purpose of going from Markdown to PDF. Give it a try!. It uses marked.js under the hood, and presents a live preview rendered on a Letter-size (8.5 in. x 11 in.) page.

If you are trying to render this in the browser, we can use the marked library in order to convert the markdown into HTML code.

The first step is to install marked. This is a markedown parser that will convert our markdown content into HTML. Run the command below to install marked.

I'm using @std/front-matter package along with marked as my blog runs on Deno, but FM would work with anything that has markdown files in folders.

To tackle this, I created an issue detailing my planned approach. I intended to use Marked to conditionally render certain markdown elements into HTML. After diving deep into Marked's documentation, I discovered this was indeed possible - you can simply disable the elements you don't want to render into HTML!