remark VS micromark

Convert them to HTML, PDF, or other formats with minimal effort. This means your content investment remains valuable regardless of which documentation system you're using now or in the future. For this blog, we use remarkjs to convert from markdown to HTML.

This plugin is built as an extension for remark, a powerful Markdown processor. When used in conjunction with react-remark (a library for rendering Markdown as React components), remark-react-liquid-tag parses your Markdown for these special liquid tags.

Processes and Chunks Content: Using tools like gray-matter and remark (with strip-markdown), the plugin extracts frontmatter (such as titles and tags) and converts the Markdown into plain text. Then it splits this content into manageable chunks (with configurable maximum chunk size) while preserving metadata like file paths.

Both Remark and Rehype are frameworks to transform documents by first transforming them to abstract syntax trees (AST) and then applying pluggable functions to the AST before converting it to the target format.

remarkjs/remark: markdown processor powered by plugins part of the @unifiedjs collective

I also didn't try this tool but it's called RemarkJS which is named too similar to revealjs.

remark. Primarily, this is a linter for Markdown. Additionally, thanks to its numerous plugins, it allows us to perform additional checks for grammatical mistakes within the content itself. Before using this linter, our content was not scrutinized to this extent.

Rehype and Remark are plugins used to transform and manipulate the HTML and Markdown content of a website, helping to enhance its functionality and appearance.

I usually combine remark-parse, remark-rehype and rehype-react to transform markdown into react components. The configuration of the processor is like:

Astro content collection are as simple as a folder containing a bunch of Markdown (or Markdoc or MDX) files if that's the only thing you need, but they can also do relationship matching between different collections, frontmatter validation using zod and you can also customize how the markdown is parsed and translated to html using rehype and remark and their plugin ecosystem.

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.