Markdeep VS ShowdownJS

It could be that I'm just one of the 10,000 some days (https://xkcd.com/1053/) but there has been a few times that I've seen an article on HN and went "Umm, I didn't know I needed that, but it fits into a niche use that I have." My last one was Markdeep in a discussion about markup languages. https://casual-effects.com/markdeep/ Or Picotron (https://news.ycombinator.com/item?id=39786984)... - Source: Hacker News / about 1 month ago

I didn't see anyone mention Markdeep [0] yet. I started with a notes.txt file for the system I maintain. I found myself gradually adopting Markdown syntax because I need bulleted lists and headings to separate different sections. I also needed hyperlinks to documentation or StackOverflow answers. So one day I just added the Markdeep tags to the bottom of the file and renamed it to notes.md.html I still keep it... - Source: Hacker News / 2 months ago

Don't discount #2 there. I still make and use ASCII art when commenting source code. Flow charts! ASCII art diagrams can be automatically rendered to an image, too: https://casual-effects.com/markdeep/. - Source: Hacker News / 4 months ago

I started using MarkDown tools that support MathJax. As my preferred environment is as simple as possible I'm using Markdeep (https://casual-effects.com/markdeep/) and hammer and chisel (aka vi). Working well for me. Source: 8 months ago

I never tried using vim wiki because I was already using markdeep for a similar purpose. I could write markdown from the comfort of vim, then get rendering in a browser basically for free. I have toyed with the idea of creating a custom version of the vim wiki plugin which creates .md.html pages with the markdeep script code in the appropriate place. Thus allowing for the best of both worlds: fast editing in vim... Source: 11 months ago

So you're going to need a Markdown parser that produces HTML. But there's a question of where is the data coming from and where you you want to process it? If it's going to be all on the frontend like a text editor, use a JS library for it (a quick google search produces ShowdownJS). Source: over 1 year ago

Previously, I was required to implement the markdown support manually which meant that the use of public libraries was prohibited. My tool could only support limited styling elements such as header1, header2, links, bold and italics, but now I can finally let my tool have a full markdown support by using Showdown. - Source: dev.to / over 1 year ago

The first two ages are very heavy on content so I decided to use markdown and tailwind’s typography plugin for styling. I also used showdown to fetch the markdown and turn it into HTML. The code for the above can be found on the site’s GitHub repository. - Source: dev.to / over 1 year ago

I'm using https://github.com/showdownjs/showdown for the core rendering-markdown functionality, with a bunch of additional listeners etc on top of it to fit it into the notion-style UX! Hope that helps :). Source: over 1 year ago

It looks like it uses showdown as the engine. Source: almost 2 years ago