markdown / discussion Goto Github PK

<<< starts a quote block, >>> ends it.
Example:

<<<JoeLocke:discord.com
I never liked MCU anyway.
>>>

(here, similar to codeblock language on the same line as the code block's opener, the citation is right after the quoteblock opener.)

Hey, I just wanted to let you know that Standard Markdown happened, and since you have already made an effort to standardize Markdown, I wanted to invite you over there to join the discussion and work on the standard together!

Recent discussion on the Markdown mailing list has resulted in several suggestions as to syntax for the time element introduced in HTML5.

Wrapped text, wrapped datetime

The conference commences on [30 May 2011]{2011-05-30T15:00-07:00}.

Wrapped text, implicit reference

The conference commences on [30 May 2011].

[30 May 2011]: datetime: 2011-05-30T15:00-07:00

(The pubdate attribute could be supported by appending ", pubdate" to the definition.)

Bracketless text, implicit reference

The conference commences on 30 May 2011.

*[30 May 2011]: 2011-05-30 15:00 -07:00

This is an extension of PHP Markdown Extra's abbreviation syntax. It also highlights the possibility of formatting the datetime attribute in a more human-friendly manner.

(The pubdate attribute could be supported by appending ", pubdate" to the definition.)

The biggest users of markdown really just need a js implementation (StackExchange, GH, Meteor)

Standardizing on a js implementation means less spec work and we will have an official spec sooner.

Direct them to markdown.github.com, or the wiki or the issues page etc.

Needs more levels for the bullet lists:

On Githubs version:

* level 1
 * level 2
  * level 3
   * level 4

...equals:

• level 1
  • level 2
  • level 3
  • level 4

And the same for the numbered lists so you can do stuff like this:

1. level 1
 1. level 2
  1. level 3
   1. level 4

...and get this:

1. level 1
 a. level 2
  i. level 3
   ?. level 4

...instead of:

1. level 1
   1. level 2
   2. level 3
   3. level 4

Need to get issue labels up in here...

https://github.com/freesurface/get-diagrams

The idea is pretty simple... Make a service that uses get params to build diagrams as you write. The goal being to better facilitate a continuous train of thought. The way that markdown deals with new lines ends up making the schema pretty decent to look at. As of right now the service uses phantomjs to parse a document which runs a really cool tool that uses Jison to turn natural language into sequence diagrams.

https://github.com/bramp/js-sequence-diagrams

I have been having a lot of success getting non-tech writers into markdown and github in general. I'd love some thoughts around this. Does it have potential? Seem useful? I am thinking Venn diagrams would be a nice option.

Here is an example of what I have so far (still buggy)...

![sequence](http://get-diagrams.com/sequence?json=[
    "Andrew-->China: Says Hello",
    "Note right of China: China thinks about it",
    "China-->Andrew: How are you?",
    "Andrew-->>China: I am goodie thanks!"
    ])

Results in this...
![sequence](http://get-diagrams.com/sequence?json=[
"Andrew-->China: Says Hello",
"Note right of China: China thinks about it",
"China-->Andrew: How are you?",
"Andrew-->>China: I am goodie thanks!"
])

There are a few test suites around. It might be worth to mention them. Ciro Santilli is actively contributing to the one I'm hosting: markdown testsuite.