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.
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?
I’m not sure what’s the use case for this, but for static content seems wasteful and a bad idea in general.
They do use YAML FrontMatter for attaching metadata so the CMS knows how to process certain pages (e.g. page title, page type etc.), but it isn't too complicated in practice: https://learn.getgrav.org/17/content/content-pages#page-file
They also have an admin plugin, which you can use if you prefer a more traditional workflow, even if it just generates the same file format under the hood: https://learn.getgrav.org/16/admin-panel/introduction
I'm actually using an ancient version of Grav for my own blog, although I had to put the admin path behind additional auth (in addition to the one it already provides), for safety: https://blog.kronis.dev/
I really like hybrid systems like that: a CMS for blogging or just writing in general that's based on Markdown, generates static files for decent performance, but is also extensible with additional functionality, and also has a decent web UI if you want one.
(there are probably other CMSes like that out there, or more generic solutions, too)
Of course, the actual use case for the linked solution is a bit different, being able to dynamically render Markdown client side is also pretty cool! Feels almost more flexible in a way.
Believe there may also be something similar for Apache?
Another alternative that I would suggest is to just serve the files directly (in Markdown or Gemini or PDF or whatever other format they might be). To allow working in a web browser, one idea is to try to implement my idea of a Interpreter response header in web browser, which would be used if the web browser does not understand the file format (if the user has not disabled the use of the Interpreter header). This way, potentially any file format can be implemented.
There is also question about different variants of Markdown. Well, the way to indicate that is by parameters in the MIME type, I think; you can specify if it is Commonmark or something else. This way you can tell which variant it is.
One problem with MIME is that indicating multiple file formats does not work very well. UTI specifies that it is a specific kind of another file format but it must be specified in another file instead of this one and does not have parameters, and has other problems, so UTI is not good either. That is why I wanted to make the "unordered labels file identification" which you can specify, in the same identification, multiple types/parameters, e.g. "text:plaintext:markdown+commonmark".
If anybody uses both showdown.js and this casual-markdown.js, could you give some comments?
<html> <body> <div class="accordion"> <div class="accordion-item" title="..."> text with markdown syntax goes here </div> </div> <script> // use showdown.js to convert the innerHTMLin .md syntax to html code // use bootstrap to make the accordion-item collapsible/expandable // use js to make a floating TOC </script> </body> </html>
The idea is that having it server-side allows for the page to be cached by a CDN (e.g. CloudFlare), so you end up serving static HTML, with better performance and SEO than JS-compiled markdown.
Which isn't in the github repo.
(I've used markdown for note taking, not for web pages, hence am asking.)