micromark VS remarkable

You mean when fetching the data on the client, you don't want it to come along with the styling? Is it in a tag?

I just want to wrap my head around the problem more properly, and what you're trying to solve

Also, if the blog post data was created with styling in the first place then what's the purpose for removing the styling? The only reason I can imagine is that the same blog post data would be used for two different purposes, one needing the styled version while the other would need the unstyled version. Otherwise, if the data is only ever going to be used without styles, I would just make sure they're added without styles in the first

Also, if you want to store markdown instead of html in the database, you can parse it into HTML on the client using a library like micromark (https://github.com/micromark/micromark) or similar

React markdown vs remark react-markdown is a library that provides the React component to render the Markdown markup while remark is a markdown preprocessor built on micromark. It inspects, parses and transforms markdowns.

> we can't take some well-tested, used-by-millions library

You can.

Here is an example of Sciter application that uses RemarkableJS library (https://github.com/jonschlinkert/remarkable) as it is:

https://quark.sciter.com/quark-application-samples/hello-mar...

Since then they've made things that are IMO quite useful, like enquirer, micromatch, and remarkable.

mdview (sources) uses RemarkableJS for MD->HTML conversion.

will give you split-view out-of-the-box. But web dev's will start looking for frameworks in order to achieve this simple task that browser have internally already.

TL;DR: Web and desktop UIs use inherently different models. You can share parts between these two different platforms but only parts, really.

[1] Remarkable JS: https://github.com/jonschlinkert/remarkable