We should have Markdown-rendered websites • Hacker News Board

Re: We should have Markdown-rendered websites

#91

Post by varispeed » Thu, Nov 10, 2022, 5:32 PM UTC

Can someone explain what is the point of ipfs? I visited the homepage and it mostly shows an information about what it is not and disadvantages of things that are not ipfs.

But I am struggling to understand why would I want to use it and how?

For instance, can I host a website on it? Can I put a wordpress on it? How can I share my website with someone? Can I use my own domain? Or is it like FTP? I really don't get it and feels like I am missing out.

Re: We should have Markdown-rendered websites

#92

Post by donatj » Thu, Nov 10, 2022, 5:35 PM UTC

You could presumably just add a single line of JS to a markdown file that would render it as HTML.

Re: We should have Markdown-rendered websites

#93

Post by LAC-Tech » Thu, Nov 10, 2022, 5:35 PM UTC

xigoi wrote: post #35

Gemini. You're describing Gemini. https://gemini.circumlunar.space/

Gemtext is a bit less capable than markdown, isn't it? IE there's no inline images.

Re: We should have Markdown-rendered websites

#94

Post by ihatepython » Thu, Nov 10, 2022, 5:36 PM UTC

thih9 wrote: post #68

lake_vincent wrote: post #12

Earlier quoted context omitted.

Let's just embrace the chaos and develop a new flavor for every browser until there are precisely 31 different flavors of Markdown. We cap it there, Baskin Robbins style, and then watch the world burn.

We could have a higher level language and tooling that transpiles everything to all known markdown flavors and bundles them all. But I guess one of these 31 flavors already does that.

I would be on-board with this as long as we compile everything into WebAssembly with Emscripten first

Re: We should have Markdown-rendered websites

#95

Post by 2OEH8eoCRo0 » Thu, Nov 10, 2022, 5:37 PM UTC

I hate markdown. Try to find a list of supported syntax highlighting for code blocks.

Re: We should have Markdown-rendered websites

#96

Post by fedeb95 » Thu, Nov 10, 2022, 5:38 PM UTC

The article should probably read: we should write more simple websites. A few lines of css does the trick, usually. That's what I do in my tiny website http://scriptkid.it I learned from someone who posted here on HN the

trick.

Re: We should have Markdown-rendered websites

#97

Post by krono » Thu, Nov 10, 2022, 5:39 PM UTC

ElevenLathe wrote: post #71

jmull wrote: post #48

This doesn't really make sense, for a couple reasons... There are many flavors of markdown. We'd need a standards body, compatibility suites, etc., and for all the browser vendors to adopt it. Meanwhile, markdown is designed to transform to HTML, which browsers already render. Adding a markdown-to-html plugin/step to your web server or publishing process is not exactly the most burdensome thing, relative to everythin…

I get this, but OTOH it is IMO best to distribute digital artifacts in the format that is most useful for editing or creating derivative works. This is the free software philosophy but also a societal good. Many of us learned HTML and web technologies by reading the source code of websites, and we've closed that door behind us with all of the build steps that turn our actual code into a computer-readable-only mess wh…

Sourcemaps for HTML essentially.

Re: We should have Markdown-rendered websites

#98

Post by paxys » Thu, Nov 10, 2022, 5:39 PM UTC

This misses the real point of Markdown, which isn't to be simple or opinionated but to be readable by the end user in both forms (raw or rendered).

In case of a web site there is never the expectation of the source being easy to read for the end user. If you want to create a simple page – great, go for it. The only minor change will be replacing markdown tags with HTML ones. And there's plenty of tooling which does that trivially.

Re: We should have Markdown-rendered websites

#99

Post by xigoi » Thu, Nov 10, 2022, 5:42 PM UTC

LAC-Tech wrote: post #93

xigoi wrote: post #35

Gemini. You're describing Gemini. https://gemini.circumlunar.space/

Gemtext is a bit less capable than markdown, isn't it? IE there's no inline images.

The whole point is that the client decides the presentation. If it wants to display images as inline, it will, if not, it won't.

Re: We should have Markdown-rendered websites

#100

Post by mdaniel » Thu, Nov 10, 2022, 5:44 PM UTC

Shtirlic wrote: post #40

It's already done in Gemini protocol with Gemtext format ( https://gemini.circumlunar.space/docs/gemtext.gmi )

> This is the only supported list syntax. Using - instead of * like in Markdown will not do anything. Nested lists are not supported.

yeah, no. I can't tell if this is some kind of parody or what