github-markdown/markdown.md
2021-08-08 17:29:42 -04:00

448 lines
9.5 KiB
Markdown

# The Cheat Sheet
## Table of Contents
[Headers](#headers)
[Emphasis](#emphasis)
[Lists](#lists)
[Links](#links)
[Images](#images)
[Code and Syntax Highlighting](#code-and-syntax-highlighting)
[Tables](#tables)
[Blockquotes](#blockquotes)
[Inline HTML](#inline-html)
[Horizontal Rule](#horizontal-rule)
[Line Breaks](#line-breaks)
[Youtube videos](#youtube-videos)
***
### Headers
Code:
```no-highlight
# H1
## H2
### H3
#### H4
##### H5
###### H6
Alternatively, for H1 and H2, an underline-ish style:
Alt-H1
======
Alt-H2
------
```
Results:
# H1
## H2
### H3
#### H4
##### H5
###### H6
Alternatively, for H1 and H2, an underline-ish style:
Alt-H1
======
Alt-H2
------
***
### Emphasis
Code:
```no-highlight
Emphasis, aka italics, with *asterisks* or _underscores_.
Strong emphasis, aka bold, with **asterisks** or __underscores__.
Combined emphasis with **asterisks and _underscores_**.
Strikethrough uses two tildes. ~~Scratch this.~~
<ins>Underline this part</ins>
```
Results:
Emphasis, aka italics, with *asterisks* or _underscores_.
Strong emphasis, aka bold, with **asterisks** or __underscores__.
Combined emphasis with **asterisks and _underscores_**.
Strikethrough uses two tildes. ~~Scratch this.~~
<ins>Underline this part</ins>
***
### Lists
Code:
```no-highlight
1. First ordered list item
2. Another item
* Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
1. Ordered sub-list
4. And another item.
Some text that should be aligned with the above item.
* Unordered list can use asterisks
- Or minuses
+ Or pluses
```
Results:
1. First ordered list item
2. Another item
* Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
1. Ordered sub-list
4. And another item.
Some text that should be aligned with the above item.
* Unordered list can use asterisks
- Or minuses
+ Or pluses
***
### Links
There are two ways to create links.
```no-highlight
[I'm an inline-style link](https://www.google.com)
[I'm a reference-style link][Arbitrary case-insensitive reference text]
[You can use numbers for reference-style link definitions][1]
Or leave it empty and use the [link text itself][]
Some text to show that the reference links can follow later.
[arbitrary case-insensitive reference text]: https://www.mozilla.org
[1]: http://slashdot.org
[link text itself]: http://www.reddit.com
```
[I'm an inline-style link](https://www.google.com)
[I'm a reference-style link][Arbitrary case-insensitive reference text]
[You can use numbers for reference-style link definitions][1]
Or leave it empty and use the [link text itself][]
Some text to show that the reference links can follow later.
[arbitrary case-insensitive reference text]: https://www.mozilla.org
[1]: http://slashdot.org
[link text itself]: http://www.reddit.com
***
### Images
Code:
```no-highlight
Here's our logo (hover to see the title text):
Inline-style:
![alt text](https://raw.githubusercontent.com/kjodle/d12-message-blocks/
master/images/acorn.png "Logo Title Text 1")
Reference-style:
![alt text][logo]
[logo]: https://raw.githubusercontent.com/kjodle/d12-message-blocks/
master/images/acorn.png "Logo Title Text 2"
```
Results:
Here's our logo (hover to see the title text):
Inline-style:
![alt text](https://raw.githubusercontent.com/kjodle/d12-message-blocks/master/images/acorn.png "Logo Title Text 1")
Reference-style:
![alt text][logo]
[logo]: https://raw.githubusercontent.com/kjodle/d12-message-blocks/master/images/acorn.png "Logo Title Text 2"
***
### Code and Syntax Highlighting
Code blocks are part of the Markdown spec, but syntax highlighting isn't. However, many renderers(including Github's and Gitea's) support syntax highlighting. *Markdown Here* supports highlighting for dozens of languages (and not-really-languages, like diffs and HTTP headers).
Code:
```no-highlight
Inline `code` has `back-ticks around` it.
```
Results:
Inline `code` has `back-ticks around` it.
Blocks of code are either fenced by lines with three back-ticks <code>```</code>, or are indented with four spaces. I recommend only using the fenced code blocks -- they're easier and only they support syntax highlighting.
Code:
```
```javascript
var s = "JavaScript syntax highlighting";
alert(s);
```
```python
s = "Python syntax highlighting"
print s
```
```
No language indicated, so no syntax highlighting.
But let's throw in a <b>tag</b>.
```
```
Results:
```javascript
var s = "JavaScript syntax highlighting";
alert(s);
```
```python
s = "Python syntax highlighting"
print s
```
```
No language indicated, so no syntax highlighting in Markdown Here
(varies on Github).
But let's throw in a <b>tag</b>.
```
(Github Wiki pages don't seem to support syntax highlighting, so the above won't be colourful (the strings are not red, for example). Try it out in a Github Markdown README or Github Issue -- you can preview a new Issue without submitting it.)
Again, to see what languages are available for highlighting, and how to write those language names, see the [highlight.js demo page](http://softwaremaniacs.org/media/soft/highlight/test.html).
***
### Tables
Tables aren't part of the core Markdown spec, but they are part of GFM and Gitea does support them.\
Code:
```no-highlight
Colons can be used to align columns.
| Tables | Are | Cool |
| ------------- |:-------------:| -----:|
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |
The outer pipes (|) are optional, and you don't need to make the raw
Markdown line up prettily. You can also use inline Markdown.
Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3
```
Results:
Colons can be used to align columns.
| Tables | Are | Cool |
| ------------- |:-------------:| -----:|
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |
The outer pipes (|) are optional, and you don't need to make the raw Markdown line up prettily. You can also use inline Markdown.
Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3
***
### Blockquotes
Code:
```no-highlight
> Blockquotes are very handy in email to emulate reply text.
> This line is part of the same quote.
Quote break.
> This is a very long line that will still be quoted properly when it wr
aps. Oh boy let's keep writing to make sure this is long enough to actua
lly wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.
```
Results:
> Blockquotes are very handy in email to emulate reply text.
> This line is part of the same quote.
Quote break.
> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.
***
### Inline HTML
You can also use raw HTML in your Markdown, and it'll mostly work pretty well.
Code:
```no-highlight
<dl>
<dt>Definition list</dt>
<dd>Is something people use sometimes.</dd>
<dt>Markdown in HTML</dt>
<dd>Does *not* work **very** well. Use HTML <em>tags</em>.</dd>
</dl>
```
Results:
<dl>
<dt>Definition list</dt>
<dd>Is something people use sometimes.</dd>
<dt>Markdown in HTML</dt>
<dd>Does *not* work **very** well. Use HTML <em>tags</em>.</dd>
</dl>
***
### Horizontal Rule
Code:
```
Three or more...
---
Hyphens
***
Asterisks
___
Underscores
```
Results:
Three or more...
---
Hyphens
***
Asterisks
___
Underscores
***
### Line Breaks
My basic recommendation for learning how line breaks work is to experiment and discover -- hit &lt;Enter&gt; once (i.e., insert one newline), then hit it twice (i.e., insert two newlines), see what happens. You'll soon learn to get what you want. "Markdown Toggle" is your friend.
Here are some things to try out:
Code:
```
Here's a line for us to start with.
This line is separated from the one above by two newlines, so it will be
a *separate paragraph*.
This line is also a separate paragraph, but...
This line is only separated by a single newline, so it's a separate line
in the *same paragraph*.
```
Results:
Here's a line for us to start with.
This line is separated from the one above by two newlines, so it will be a *separate paragraph*.
This line is also begins a separate paragraph, but...
This line is only separated by a single newline, so it's a separate line in the *same paragraph*.
(Technical note: *Markdown Here* uses GFM line breaks, so there's no need to use MD's two-space line breaks.)
### Youtube videos
They can't be added directly but you can add an image with a link to the video like this:
Code:
```no-highlight
<a href="http://www.youtube.com/watch?feature=player_embedded&v=sg90VJjZ
PKU " target="_blank"><img src="http://img.youtube.com/vi/sg90VJjZPKU/0.
jpg" alt="IMAGE ALT TEXT HERE" width="240" height="180" border="10" />
</a>
```
Results:
<a href="http://www.youtube.com/watch?feature=player_embedded&v=sg90VJjZPKU" target="_blank"><img src="http://img.youtube.com/vi/sg90VJjZPKU/0.jpg" alt="IMAGE ALT TEXT HERE" width="240" height="180" border="10" /></a>
Or, in pure Markdown, but losing the image sizing and border:
Code:
```no-highlight
[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/sg90VJjZPKU/0.jpg)](ht
tps://www.youtube.com/watch?v=sg90VJjZPKU)
```
Results:
[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/sg90VJjZPKU/0.jpg)](https://www.youtube.com/watch?v=sg90VJjZPKU)
The main difference is that the former method allows you to add `target="_blank"` to the `<a>` tag.