Vue UI at runtime, zero build step

(markdown-ui.com)

193 points yaoke259 | 1 comments | 26 Aug 25 10:13 UTC | HN request time: 0.211s | source

Show context

lelanthran ◴[26 Aug 25 11:00 UTC] No.45024882[source]▶

Maybe I'm not understanding, but why is this "Turn Markdown into React/Svelte/Vue UI" and not "Turn Markdown into HTML"?

I'm not seeing the value of generating React, Vue or Svelte as opposed to generating DOM components.

replies(7): >>45024990 #>>45025096 #>>45025261 #>>45025292 #>>45025332 #>>45029796 #>>45030644 #

threetonesun ◴[26 Aug 25 11:56 UTC] No.45025292[source]▶

>>45024882 #

It's very silly. Given that Markdown fully supports HTML I have built sites using just Markdown + web components but that's... just how it works.

What's really needed is a better editor experience.

replies(3): >>45025497 #>>45026263 #>>45026925 #

1. lelanthran ◴[26 Aug 25 13:27 UTC] No.45026263[source]▶

>>45025292 #

> Given that Markdown fully supports HTML I have built sites using just Markdown + web components but that's... just how it works.

Agreed. My blog is a single shell script that runs pandoc on all the files in a subdir, generates a new .md file for table of contents, and then uses pandoc to generate a ToC.html file.

That doesn't mean that my the site uses no Javascript - the magic of web components means that I can place `<some-custom-component> ...` in the middle of my .md content and have interactive components in the resulting html.

What would be really useful is decent tooling for this sort of authoring.

↑