remark-directive VS MDsveX

Fortunately, we don't have to write any code as there is remark-directive that does exactly what we need.

The projects this solutions works with are customised Sveltekit projects I made. It has everything: markdown parser using Mdsvex, image converting tool using vite-imagetools, it has toml parser, and of course live preview and lots of other smaller things like markdown directives.

The coolest thing is that MDSveX hooks into remark and rehype, which provides a whole ecosystem of plugins to choose from.

No, not formally, but there are plugins for the various process that implement it based on the spec I linked to, like markdown-it and remark.

In the ever-evolving world of web development, content remains king. For sites heavy with documentation, blogs, guides, changelogs, or engineering wikis, Markdown has emerged as the go-to language for crafting readable, maintainable content. However, the standard Markdown might not always fit the bill, especially when you're looking to add a unique touch or specific functionality to your Svelte-powered websites. Enter mdsvex - a Svelte preprocessor that not only understands Markdown but extends its capabilities, allowing developers to introduce custom-flavored Markdown.

I was working on my blog websites. The current method I use to add more posts is using mdsvex(https://github.com/pngwn/MDsveX) it turns my markdown files into post.

Oh right sorry. MDSVEX is a preprocessor for using Svelte components in markdown files. SVX is just the file format for it

If mdsvex is not applicable, I would still look through it's sources to see how they handle it and maybe find some useful ideas. Looks like there are multiple packages that handle all that parsing and preparing: https://github.com/pngwn/MDsveX/tree/master/packages

You can use those components in plain markdown. We will have to write documentation for inlang. Instead of requiring a preprocessor like MDX, MDsvex, or Stripe Markdoc, web components can be used instead. Reducing boilerplate, increasing maintainability and last but not least the community does not have to reinvent the wheel for every markdown preprocessor. Just use the platform. Just use web components in markdown.

SvelteKit plus mdsvex. There are quite a few examples out there, e.g. https://github.com/rodneylab/sveltekit-blog-mdx.

One issue we previously had with parsing Markdown with MDsveX was how to get a list of blogs without embedding all the blog content into some JS files... There's quite a few posts online and that's why I figured I'd talk about it here because it seems to be a common pain with SvelteKit and adapter-static. Ultimately what we did was use route parameters and different endpoints for the different requests, which you can see here.

We’re going to use mdsvex to render our Markdown posts. It’s a Markdown preprocessor for Svelte which allows you to use Svelte templating and components amongst your Markdown.