Live data from Hacker News

Show HN: Markdown as web page/site

github.com

31–40 of 60 posts

Re: Show HN: Markdown as web page/site

#31
post #5
post #4

I was under the impression that using markdown to create html webpages was a common use case, and had been solved. Was I wrong? (I've used markdown for note taking, not for web pages, hence am asking.)

I was under the same impression as well. I have been using https://docusaurus.io/ for some time now and I am very happy with it and I am pretty sure there are other tools out there as well.

reminds me of Znai [1]

What sold me on Znai was the integration of code snippets (straight from source files, mining them out of the code) and integration of diagramming from PlantUML, which is done in a way that is compatible with the format used in Gitlab, VSCode and other markdown renderers.

Markdown has turned into a truly amazing ecosystem.

[1] https://testingisdocumenting.org/znai/introduction/what-is-t...

Re: Show HN: Markdown as web page/site

#32

org-mode already has this. Unfortunately, people seem to continue to use the inferior version of org known as Markdown. It is somewhat like how pdf overtook the superior format djvu.

I agree that Markdown is probably an inferior markup format compared to org but serious usage of org is tied to Emacs. Moreover, Markdown (or CommonMark) has an extremely healthy ecosystem and a lot of tools that make life easier, unlike org mode. The most popular static site generators also use Markdown and RST. Unless using Emacs becomes a user friendly beginner's choice (which it isn't, and that's fine) or Org is…

A handful of folks, myself included, are breaking org out of Emacs, making it more accessible to all.

I built two apps for iOS:

https://flathabits.com

https://plainorg.com

There are other org-based tools out there.

https://BrainTool.org

https://logseq.com

https://orgzly.com

https://beorg.app

https://easyorgmode.com

https://organice.200ok.ch

https://orgro.org

Re: Show HN: Markdown as web page/site

#34
post #4

I was under the impression that using markdown to create html webpages was a common use case, and had been solved. Was I wrong? (I've used markdown for note taking, not for web pages, hence am asking.)

Curious if we've ever considered adding Markdown as a new MIME type that could be accepted directly by browsers (similar to text/plain). It could be nice to serve markdown without needing to even use a static-site generator (but still have the server reasonably render the doc, similar to a reader view).

Re: Show HN: Markdown as web page/site

#36

What's the reason for supporting IE9?

it is coded in vanilla javascript. i do nothing to cater IE9, it just run well. btw, believe there are some scenarios to load page within IE9 (e.g. OLE control, hta script)

FWIW there's nothing about "vanilla JavaScript" that means IE9 will be supported. It's avoiding certain language features and DOM APIs that does it.

Just adding this because it can lead to the implication that not supporting IE9 means you're trying to do something frivolous as opposed to "vanilla JavaScript".

Re: Show HN: Markdown as web page/site

#37
There appears to be many comments here, arguing that authoring web content in markdown is nothing new, and correctly so.

But this (along with md-page and mdwiki mentioned in other comments) is actually an interesting small twist on it. Regularly the conversion is done on the server side, and everything is published in html.

Here, you both author and publish in markdown.

What this library does, if I'm reading it correctly, it acts as polyfill that lets legacy evergreen browsers to consume the markdown files that you serve.

You can publish your content in a bit more simpler, yet still declarative format, without any javascript, and still make it accessible, in a properly rendered format, for evergreen browsers.

(Yes, you can still add javascript to markdown files, but it is relatively easy for the agent to just discard any javascript or html.)

The markdown is the source of truth here. No need for rendering everything twice for serving, once for html and once for markdown, and creating a point where their content might diverge.

It's straight out of gemini's playbook.

I think this is a wonderful idea, and if developed a bit further, and adopted more widely, could help push markdown to be a properly supported format in modern browsers.

The next question is, how would you get the second layer of github flavored markdown fluff (latex, mermaid, etc), that is generally not standardized, to be supported in browsers as well?

Re: Show HN: Markdown as web page/site

#40

This requires JavaScript to dynamically serve HTML. So this wastes everybody’s CPU for a deterministic computation that could be served directly. I’m not sure what’s the use case for this, but for static content seems wasteful and a bad idea in general.

The amount of CPU waste would be negligible.
Post reply on HN