We Should Have Markdown Rendered Websites

Re:We Should Have Markdown Rendered Websites by falcolas on Thursday November 10, 2022 @11:34AM (#33549013)

My personal preference would be GitHub flavored markdown, since as a coder it includes a lot of very useful non-standard markups. The compromises it makes on the non-deterministic markup elements are acceptable as well.

[ Parent | on HN ]

Re:We Should Have Markdown Rendered Websites by acomjean on Thursday November 10, 2022 @12:23PM (#33549926)

I think this makes sense.

Many of the GitHub readmes are in markdown already, so people are quite familiar with it and there might already be an open source package that renders it out…

[ Parent | on HN ]

Re:We Should Have Markdown Rendered Websites by bonestamp2 on Thursday November 10, 2022 @02:34PM (#33551853)

In fact, github itself can already render it out. Markdown based websites hosted for free on github: https://www.markdownguide.org/tools/github-pages/

[ Parent | on HN ]

Re:We Should Have Markdown Rendered Websites by acomjean on Thursday November 10, 2022 @03:30PM (#33552837)

I guess it wasn't clear, but I meant those markdowns are rendered on everyones github page.. But the whole github pages thing is new to me. Very cool and seems like what the blog post was asking for.

Its using "Jekyll" to render those "github-pages" sites https://github.com/jekyll/jekyll

[ Parent | on HN ]

Re:We Should Have Markdown Rendered Websites by toastal on Friday November 11, 2022 @01:31PM (#33564732)

Like how they're introducing admonitions syntax by overloading the blockquote sigil that makes it difficult or impossible to nest, has a heavy English bias, and doesn't even transform the underlying element making the use of blockquote unsemantic. They also just skipped the CommonMark RFC and other implementations throwing their weight into the ring with no regard for prior art. I also don't think a corporation, Microsoft, needs to be in charge of the spec either. No thank you.

[ Parent | on HN ]