Friam

Fwd: Heck Yes Markdown

Classic

List

Threaded

4 messages Options

Owen Densmore

Fwd: Heck Yes Markdown

Administrator

Speaking of static sites & markdown, this is nuts & fun!

http://heckyesmarkdown.com/

-- Owen

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Russ Abbott

Re: Fwd: Heck Yes Markdown

Not sure what it's supposed to do, but the pages I tried it on came out looking pretty bad.

On Thu, Oct 15, 2015 at 8:27 AM Owen Densmore <[hidden email]> wrote:

Speaking of static sites & markdown, this is nuts & fun!

http://heckyesmarkdown.com/

-- Owen

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Marcus G. Daniels

Re: Fwd: Heck Yes Markdown

In reply to this post by Owen Densmore

Hmm, a browser can support different MIME types, this is just another one.

I mean, one wouldn’t convert JPEG to HTML.

From: Friam [mailto:[hidden email]] On Behalf Of Owen Densmore
Sent: Thursday, October 15, 2015 9:27 AM
To: Complexity Coffee Group <[hidden email]>; Wedtech <[hidden email]>
Subject: [FRIAM] Fwd: Heck Yes Markdown

Speaking of static sites & markdown, this is nuts & fun!

http://heckyesmarkdown.com/

-- Owen

Owen Densmore

Re: Fwd: Heck Yes Markdown

Administrator

On Thu, Oct 15, 2015 at 2:31 PM, Marcus Daniels <[hidden email]> wrote:

Hmm, a browser can support different MIME types, this is just another one.

I mean, one wouldn’t convert JPEG to HTML.

An RFC?! Wow!

I knew there were folks trying to standardize markdown due to spreading "flavors" like Github Flavored Markdown, and others adding tables & other additions.

https://github.com/jgm/CommonMark

.. and they've got a good point about bugs and weird end-of-line whitespace.

Gruber had some problems, especially the initial name Standard Markdown, thus the current name CommonMark.

http://arstechnica.com/information-technology/2014/10/markdown-throwdown-what-happens-when-foss-software-gets-corporate-backing/2/

The key change from the first "standards" approach and the current one is that the current one only "fixes" Gruber's. Extensions like tables come later.

I do know that using various markdown variants is tough. GitHub screws up the 4 space indent at times in comments/issues. Still requires experiments to see what it eventually looks like!