Publish page should have markdown cheat sheet built in

[georgeowell]

What's the problem you want solved? Markdown help sheet is on the old internet.

Is there a solution you'd like to recommend? We should include a markdown cheatsheet in the application itself. I'm not exactly what this would look like. Perhaps a drop down as to not add clutter.

Not sure how this would be present on the "Comment" and "Reply" actions.

[christianbundy]

Aside: Maybe it'd be useful to make all of the documentation in the docs/ directory available in the app? We have the readme available at /meta/readme, but we could add more. Although this opens the hairball about multi-lingual documentation.

[christianbundy]

Step one: make an SSB-Markdown cheat sheet.

• _italic_
• **bold**
• # heading 1
• ## heading 2
• ### heading 3
• [link](http://example.com)
• %ssblink.sha256
• ![my image](&ssblink.sha256)
• ![audio:my song](&ssblink.sha256)
• ![video:my clip](&ssblink.sha256)
• > blockquote

• - list a
  - list b
  - list c
  

• 1. list
  2. list
  3. list
  

• --- horizontal rule
• `inline code`

• ```python
  code block
  ```
  

Maybe someone could make this suck less and put it in the repo?

---

Also newlines are treated like newlines from GitHub-flavored Markdown.

If you do something like this, with one line break, it actually does a literal line break.

Fun.

[Danie10]

This works specifically for embedding a YouTube video with its thumbnail:

[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/YOUTUBE_VIDEO_ID_HERE/0.jpg)](http://www.youtube.com/watch?v=YOUTUBE_VIDEO_ID_HERE)

[black-puppydog]

@Danie10 Oasis (and patchwork for that matter) actually refuses to embed that external thumbnail and instead shows the alt text. This is by design, to avoid people embedding tracking pixels and other nefarious things.