I had an idea a while ago. Instead of dealing with two sets of files, why not make a file that was Markdown and HTML at the same time?<p>I found this utility, which unfortunately seems to have been abandoned: https://github.com/showdownjs/showdown<p>All you need to do is add a few lines to the top of your Markdown file. Here's an example:<p>https://trivialcode.com/mdhtml_demo/demo.mdhtml<p>Take a look at the source of the .mdhtml file and you'll see what I mean.<p>If you're taking notes in Markdown this might make things a bit easier to keep organized. No need to update anything if you're exporting to HTML.<p>Thoughts? Is this a good idea? A bad one? I also wondered if generating Markdown via a web server and then converting it on the fly like this would be an interesting exercise. Seems like it'd be simpler than generating HTML.<p>I use Vim, so I've put this in my vimrc for editing:<p>autocmd BufNewFile,BufRead *.mdhtml set syntax=markdown<p>First time posting here. Let me know what you guys think.
I have taken a look at the .mdhtml file and don't know what you mean ;(<p>I you mean having one file that can contain both markdown and HTML, that's what markdown is already, since you can fallback to inline or block-level HTML in markdown.<p>If OTOH you want a HTML file that can also contain markdown (or other custom Wiki syntax, and text substitution variables, and a whole lot more), than that's available in SGML (on which HTML is based) via short references.
Isn’t texme doing what you suggest here? Or am I missing something?<p><a href="https://github.com/susam/texme" rel="nofollow">https://github.com/susam/texme</a>
Not the same thing, but have a look at the Gemini [0] protocol. It uses a markup format called Gemtext which is similar to, although less featureful than Markdown. All pages are written in and served as gemtext. There's almost no rendering done, unless your client is configured to use custom stylesheets.<p>[0]: <a href="http://gemini.circumlunar.space/" rel="nofollow">http://gemini.circumlunar.space/</a>
It’s an interesting concept. But for me personally I don’t see any practical benefits of using it.<p>On my web pages I use Hugo. Conversation is done when the CI/CD system runs Hugo.[1]<p>[1] I currently use AWS Amplify. But it’s not hard to build a small Bash script to replace it.
Sounds like a terrible idea. You loose the fallback, because Markdown treated as HTML instead of text is pretty much unreadable. (block the script to see what I mean: the rules about newlines etc in HTML do work differently)
Markdeep[0] could be an option for what you are looking for.<p>[0] <a href="https://casual-effects.com/markdeep" rel="nofollow">https://casual-effects.com/markdeep</a>