We should have Markdown-rendered websites
1–10 of 351 posts
Re: We should have Markdown-rendered websites
#2FWIW, just a couple of weeks ago we started doing that for a new sqlite subproject: https://sqlite.org/wasm
With the exception of one page, all of them are markdown, rendered on demand by the Fossil SCM. The one exception is an HTML file, which we need in order to host a small JS application.
Re: We should have Markdown-rendered websites
#3If you're interested in the history of why I wrote this article, then it originated from this Twitter thread: https://nitter.net/timdaub/status/1590731949433573377
Re: We should have Markdown-rendered websites
#4There’s prose.io which basically does this
Re: We should have Markdown-rendered websites
#5OK. Which flavor of markdown should we get every browser manufacturer to use?
Re: We should have Markdown-rendered websites
#6isn't this why HTML was invented?
agree that it'd be nice to have a markdown file be rendered inherently within the browser so i don't have to use haroopad on my windows machine, but it feels like we're just going to reinvent HTML
Re: We should have Markdown-rendered websites
#7OK. Which flavor of markdown should we get every browser manufacturer to use?
Asciidoc.
Re: We should have Markdown-rendered websites
#8There’s prose.io which basically does this http://prose.io/
See also https://prose.sh (I guess `prose` is a popular name in this space) and https://bearblog.dev.
Re: We should have Markdown-rendered websites
#9why not OrgMode websites? it handles tables too!
Re: We should have Markdown-rendered websites
#10Recently there was a thread about GitHub Blocks, interactive elements within READMEs and Markdown files in general. If we could standardize that and support it, that would be cool.
Also, isn't this basically what HTML does anyway?