In which we list tips, tricks, and reminders.
- Style
- Links
- Images
- Headers
- Lists
- Blockquotes
- Code Spans
- Code Blocks
- Horizontal Rules
- Manual Line Breaks
Official documentation:
italic
*italic* bold
**bold**italic
_italic_ bold
__bold__[Inline](http://url.com/ "Inline example")[Reference-style][id] with labels (titles are optional). [id]: http://example.com/ "Reference-style example"
[Reference-style][id] with labels (titles are optional).
[id]: http://example.com/ "Reference-style example"Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"Setext-style:
Header 1
========
Header 2
--------atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6Ordered, without paragraphs:
1. Foo
2. BarUnordered, with paragraphs:
* A list item.
With multiple paragraphs.
* BarYou can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.`<code>` spans are delimited
by backticks.
You can include literal backticks
like `` `this` ``.Indent every line of a code block by at least 4 spaces or 1 tab.
This is a normal paragraph.
This is a preformatted
code block.Use three backticks to fence code blocks for better syntax-highlighting support, but note that this is a Github GFM convention.
```coffeescript
hi = (name) ->
print "hello #{name}!"
hi __filename
```Three or more dashes or asterisks:
---
* * *
- - - - End a line with two or more spaces:
Roses are red,
Violets are blue.