git format markdown

# markdown format git

---

Markdown write

GitLab Flavored Markdown $GFM$

Note: Not all of the GitLab-specific extensions to Markdown that are described in this document currently work on our documentation website.

For the best result, we encourage you to check this document out as rendered by GitLab: markdown.md

GitLab uses the Redcarpet Ruby library for Markdown processing.

GitLab uses "GitLab Flavored Markdown" $GFM$. It extends the standard Markdown in a few significant ways to add some useful functionality. It was inspired by GitHub Flavored Markdown.

You can use GFM in the following areas:

comments issues merge requests milestones snippets $the snippet must be named with a .md extension$ wiki pages markdown documents inside the repository

You can also use other rich text files in GitLab. You might have to install a dependency to do so. Please see the github-markup gem readme for more information.

Newlines

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#newlines](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#newlines)

GFM honors the markdown specification in how paragraphs and line breaks are handled.

A paragraph is simply one or more consecutive lines of text, separated by one or more blank lines. Line-breaks, or softreturns, are rendered if you end a line with two or more spaces:

Roses are red \[followed by two or more spaces\]  
Violets are blue

Sugar is sweet Roses are red Violets are blue

Sugar is sweet

Multiple underscores in words

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#multiple-underscores-in-words](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#multiple-underscores-in-words)

It is not reasonable to italicize just part of a word, especially when you're dealing with code and names that often appear with multiple underscores. Therefore, GFM ignores multiple underscores in words:

perform\_complicated\_task

do\_this\_and\_do\_that\_and\_another\_thing perform\_complicated\_task

do\_this\_and\_do\_that\_and\_another\_thing

URL auto-linking

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#url-auto-linking](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#url-auto-linking)

GFM will autolink almost any URL you copy and paste into your text:

* [https://www.google.com](https://www.google.com)
* [https://google.com/](https://google.com/)
* ftp://ftp.us.debian.org/debian/
* smb://foo/bar/baz
* irc://irc.freenode.net/gitlab
* [http://localhost:3000](http://localhost:3000)

[https://www.google.com](https://www.google.com) [https://google.com/](https://google.com/) ftp://ftp.us.debian.org/debian/ smb://foo/bar/baz irc://irc.freenode.net/gitlab [http://localhost:3000](http://localhost:3000)

Multiline Blockquote

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#multiline-blockquote](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#multiline-blockquote)

On top of standard Markdown blockquotes, which require prepending &gt; to quoted lines, GFM supports multiline blockquotes fenced by &gt;&gt;&gt;:

> > &gt; If you paste a message from somewhere else

that

spans

multiple lines,

you can quote that without having to manually prepend `>` to every line!

> > &gt;

If you paste a message from somewhere else

that

spans

multiple lines,

you can quote that without having to manually prepend &gt; to every line!

Code and Syntax Highlighting

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#code-and-syntax-highlighting](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#code-and-syntax-highlighting)

GitLab uses the Rouge Ruby library for syntax highlighting. For a list of supported languages visit the Rouge website.

Blocks of code are either fenced by lines with three back-ticks \`\`\`, or are indented with four spaces. Only the fenced code blocks support syntax highlighting:

Inline `code` has `back-ticks around` it. Inline code has back-ticks around it.

Example:

```javascript
var s = "JavaScript syntax highlighting";
alert(s);
```

```python
def function():
    #indenting works just fine in the fenced code block
    s = "Python syntax highlighting"
    print s
```

```ruby
require 'redcarpet'
markdown = Redcarpet.new("Hello World!")
puts markdown.to_html
```

```text
No language indicated, so no syntax highlighting.
s = "There is no highlighting for this."
But let's throw in a <b>tag</b>.
```

becomes:

var s = "JavaScript syntax highlighting"; alert$s$; def function:

```text
#indenting works just fine in the fenced code block
s = "Python syntax highlighting"
print s
```

require 'redcarpet' markdown = Redcarpet.new$"Hello World!"$ puts markdown.to\_html No language indicated, so no syntax highlighting. s = "There is no highlighting for this." But let's throw in a **tag**.

Inline Diff

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#inline-diff](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#inline-diff)

With inline diffs tags you can display additions or deletions .

The wrapping tags can be either curly braces or square brackets additions or deletions .

Examples:

* {+ additions +}
* \[+ additions +\]
* {- deletions -}
* \[- deletions -\] However the wrapping tags cannot be mixed as such:
* {+ additions +\]
* \[+ additions +}
* {- deletions -\]
* \[- deletions -}

Emoji

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#emoji](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#emoji)

Sometimes you want to :monkey: around a bit and add some :star2: to your :speech\_balloon:. Well we have a gift for you:

:zap: You can use emoji anywhere GFM is supported. :v:

You can use it to point out a :bug: or warn about :speak\_no\_evil: patches. And if someone improves your really :snail: code, send them some :birthday:. People will :heart: you for that.

If you are new to this, don't be :fearful:. You can easily join the emoji :family:. All you need to do is to look up on the supported codes.

Consult the [Emoji Cheat Sheet](https://www.emojicopy.com) for a list of all supported emoji codes. :thumbsup: Sometimes you want to ? around a bit and add some ? to your ?. Well we have a gift for you:

⚡ You can use emoji anywhere GFM is supported. ✌

You can use it to point out a ? or warn about ? patches. And if someone improves your really ? code, send them some ?. People will ❤ you for that.

If you are new to this, don't be ?. You can easily join the emoji ?. All you need to do is to look up on the supported codes.

Consult the Emoji Cheat Sheet for a list of all supported emoji codes. ?

Special GitLab References

GFM recognizes special references.

You can easily reference e.g. an issue, a commit, a team member or even the whole team within a project.

GFM will turn that reference into a link so you can navigate between them easily.

GFM will recognize the following:

input references

@user\_name specific user

@group\_name specific group

@all entire team

## 12345

issue

!123 merge request

$123 snippet

~123 label by ID

~bug one-word label by name

~"feature request" multi-word label by name

%123 project milestone by ID

%v1.23 one-word milestone by name

%"release candidate" multi-word milestone by name

9ba12248 specific commit

9ba12248...b19a04f5 commit range comparison

[README](doc/README) repository file references

[README](doc/README#L13) repository file line references

GFM also recognizes certain cross-project references:

input references

namespace/project\#123 issue

namespace/project!123 merge request

namespace/project%123 project milestone

namespace/project$123 snippet

namespace/project@9ba12248 specific commit

namespace/project@9ba12248...b19a04f5 commit range comparison

namespace/project~"Some label" issues with given label

It also has a shorthand version to reference other projects from the same namespace:

input references

project\#123 issue

project!123 merge request

project%123 project milestone

project$123 snippet

project@9ba12248 specific commit

project@9ba12248...b19a04f5 commit range comparison

project~"Some label" issues with given label

Task Lists

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#task-lists](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#task-lists)

You can add task lists to issues, merge requests and comments. To create a task list, add a specially-formatted Markdown list, like so:

* [x] Completed task
* [ ] Incomplete task
  * [ ] Sub-task 1
  * [x] Sub-task 2
  * [ ] Sub-task 3

Completed task

Incomplete task

Sub-task 1

Sub-task 2

Sub-task 3

Tasks formatted as ordered lists are supported as well:

1. [x] Completed task
2. [ ] Incomplete task
   1. [ ] Sub-task 1
   2. [x] Sub-task 2

Completed task

Incomplete task

Sub-task 1

Sub-task 2

Task lists can only be created in descriptions, not in titles. Task item state can be managed by editing the description's Markdown or by toggling the rendered check boxes.

Videos

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#videos](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#videos)

Image tags with a video extension are automatically converted to a video player.

The valid video extensions are .mp4, .m4v, .mov, .webm, and .ogv.

Here's a sample video:

Sample Video

Math

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#math](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#math)

It is possible to have math written with the LaTeX syntax rendered using KaTeX.

Math written inside $\`\`$ will be rendered inline with the text.

Math written inside triple back quotes, with the language declared as math, will be rendered on a separate line.

Example:

This math is inline $`a^2+b^2=c^2`$.

This is on a separate line

```text
a^2+b^2=c^2
```

Becomes:

This math is inline a2+b2=c2a^2+b^2=c^2a2+b2=c2.

This is on a separate line

a2+b2=c2a^2+b^2=c^2a2+b2=c2 Be advised that KaTeX only supports a subset of LaTeX.

Note: This also works for the asciidoctor :stem: latexmath. For details see the asciidoctor user manual.

Colors

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#colors](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#colors)

It is possible to have color written in HEX, RGB or HSL format rendered with a color indicator.

Color written inside backticks will be followed by a color "chip".

Examples:

`#F00` `#F00A` `#FF0000` `#FF0000AA` `RGB(0,255,0)` `RGB(0%,100%,0%)` `RGBA(0,255,0,0.7)` `HSL(540,70%,50%)` `HSLA(540,70%,50%,0.7)` Becomes:

## F00

## F00A

## FF0000

## FF0000AA

RGB$0,255,0$ RGB$0%,100%,0%$ RGBA$0,255,0,0.7$ HSL$540,70%,50%$ HSLA$540,70%,50%,0.7$

Supported formats:

HEX: `#RGB[A]` or `#RRGGBB[AA]`

RGB: `RGB[A](R, G, B[, A])`

HSL: `HSL[A](H, S, L[, A])`

Mermaid

Introduced in GitLab 10.3.

If this is not rendered correctly, see [https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md\#mermaid](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/markdown.md#mermaid)

It is possible to generate diagrams and flowcharts from text using Mermaid.

In order to generate a diagram or flowchart, you should write your text inside the mermaid block.

Example:

```text
graph TD;
  A-->B;
  A-->C;
  B-->D;
  C-->D;
```

Becomes:

.mermaid { / _Flowchart variables_ / / _Sequence Diagram variables_ / / _Gantt chart variables_ / /_\* Section styling_ / / _Grid and axis_ / / _Today line_ / / _Task styling_ / / _Default task_ / / _Specific task settings for the sections_/ / _Active task_ / / _Completed task_ / / _Tasks on the critical line_ / } .mermaid .label { color: \#333; } .mermaid .node rect, .mermaid .node circle, .mermaid .node ellipse, .mermaid .node polygon { fill: \#eee; stroke: \#999; stroke-width: 1px; } .mermaid .edgePath .path { stroke: \#666; stroke-width: 1.5px; } .mermaid .edgeLabel { background-color: white; } .mermaid .cluster rect { fill: \#eaf2fb !important; rx: 4 !important; stroke: \#26a !important; stroke-width: 1px !important; } .mermaid .cluster text { fill: \#333; } .mermaid .actor { stroke: \#999; fill: \#eee; } .mermaid text.actor { fill: \#333; stroke: none; } .mermaid .actor-line { stroke: \#666; } .mermaid .messageLine0 { stroke-width: 1.5; stroke-dasharray: "2 2"; marker-end: "url$\#arrowhead$"; stroke: \#333; } .mermaid .messageLine1 { stroke-width: 1.5; stroke-dasharray: "2 2"; stroke: \#333; } .mermaid \#arrowhead { fill: \#333; } .mermaid \#crosshead path { fill: \#333 !important; stroke: \#333 !important; } .mermaid .messageText { fill: \#333; stroke: none; } .mermaid .labelBox { stroke: \#999; fill: \#eee; } .mermaid .labelText { fill: white; stroke: none; } .mermaid .loopText { fill: white; stroke: none; } .mermaid .loopLine { stroke-width: 2; stroke-dasharray: "2 2"; marker-end: "url$\#arrowhead$"; stroke: \#999; } .mermaid .note { stroke: \#777700; fill: \#ffa; } .mermaid .noteText { fill: black; stroke: none; font-family: Arial, Helvetica, sans-serif; font-size: 14px; } .mermaid .section { stroke: none; opacity: 0.2; } .mermaid .section0 { fill: \#7fb2e6; } .mermaid .section2 { fill: \#7fb2e6; } .mermaid .section1, .mermaid .section3 { fill: white; opacity: 0.2; } .mermaid .sectionTitle0 { fill: \#333; } .mermaid .sectionTitle1 { fill: \#333; } .mermaid .sectionTitle2 { fill: \#333; } .mermaid .sectionTitle3 { fill: \#333; } .mermaid .sectionTitle { text-anchor: start; font-size: 11px; text-height: 14px; } .mermaid .grid .tick { stroke: \#e5e5e5; opacity: 0.3; shape-rendering: crispEdges; } .mermaid .grid path { stroke-width: 0; } .mermaid .today { fill: none; stroke: \#d42; stroke-width: 2px; } .mermaid .task { stroke-width: 2; } .mermaid .taskText { text-anchor: middle; font-size: 11px; } .mermaid .taskTextOutsideRight { fill: \#333; text-anchor: start; font-size: 11px; } .mermaid .taskTextOutsideLeft { fill: \#333; text-anchor: end; font-size: 11px; } .mermaid .taskText0, .mermaid .taskText1, .mermaid .taskText2, .mermaid .taskText3 { fill: white; } .mermaid .task0, .mermaid .task1, .mermaid .task2, .mermaid .task3 { fill: \#26a; stroke: \#194c7f; } .mermaid .taskTextOutside0, .mermaid .taskTextOutside2 { fill: \#333; } .mermaid .taskTextOutside1, .mermaid .taskTextOutside3 { fill: \#333; } .mermaid .active0, .mermaid .active1, .mermaid .active2, .mermaid .active3 { fill: \#eee; stroke: \#194c7f; } .mermaid .activeText0, .mermaid .activeText1, .mermaid .activeText2, .mermaid .activeText3 { fill: \#333 !important; } .mermaid .done0, .mermaid .done1, .mermaid .done2, .mermaid .done3 { stroke: \#666; fill: \#bbb; stroke-width: 2; } .mermaid .doneText0, .mermaid .doneText1, .mermaid .doneText2, .mermaid .doneText3 { fill: \#333 !important; } .mermaid .crit0, .mermaid .crit1, .mermaid .crit2, .mermaid .crit3 { stroke: \#b1361b; fill: \#d42; stroke-width: 2; } .mermaid .activeCrit0, .mermaid .activeCrit1, .mermaid .activeCrit2, .mermaid .activeCrit3 { stroke: \#b1361b; fill: \#eee; stroke-width: 2; } .mermaid .doneCrit0, .mermaid .doneCrit1, .mermaid .doneCrit2, .mermaid .doneCrit3 { stroke: \#b1361b; fill: \#bbb; stroke-width: 2; cursor: pointer; } .mermaid .doneCritText0, .mermaid .doneCritText1, .mermaid .doneCritText2, .mermaid .doneCritText3 { fill: \#333 !important; } .mermaid .activeCritText0, .mermaid .activeCritText1, .mermaid .activeCritText2, .mermaid .activeCritText3 { fill: \#333 !important; } .mermaid .titleText { text-anchor: middle; font-size: 18px; fill: \#333; } .mermaid g.classGroup text { fill: \#999; stroke: none; font-family: 'trebuchet ms', verdana, arial; font-size: 10px; } .mermaid g.classGroup rect { fill: \#eee; stroke: \#999; } .mermaid g.classGroup line { stroke: \#999; stroke-width: 1; } .mermaid svg .classLabel .box { stroke: none; stroke-width: 0; fill: \#eee; opacity: 0.5; } .mermaid svg .classLabel .label { fill: \#999; font-size: 10px; } .mermaid .relation { stroke: \#999; stroke-width: 1; fill: none; } .mermaid .composition { fill: \#999; stroke: \#999; stroke-width: 1; } .mermaid \#compositionStart { fill: \#999; stroke: \#999; stroke-width: 1; } .mermaid \#compositionEnd { fill: \#999; stroke: \#999; stroke-width: 1; } .mermaid .aggregation { fill: \#eee; stroke: \#999; stroke-width: 1; } .mermaid \#aggregationStart { fill: \#eee; stroke: \#999; stroke-width: 1; } .mermaid \#aggregationEnd { fill: \#eee; stroke: \#999; stroke-width: 1; } .mermaid \#dependencyStart { fill: \#999; stroke: \#999; stroke-width: 1; } .mermaid \#dependencyEnd { fill: \#999; stroke: \#999; stroke-width: 1; } .mermaid \#extensionStart { fill: \#999; stroke: \#999; stroke-width: 1; } .mermaid \#extensionEnd { fill: \#999; stroke: \#999; stroke-width: 1; } .mermaid .node text { font-family: Arial, Helvetica, sans-serif; font-size: 14px; } .mermaid div.mermaidTooltip { position: absolute; text-align: center; max-width: 200px; padding: 2px; font-family: Arial, Helvetica, sans-serif; font-size: 12px; background: \#eaf2fb; border: 1px solid \#26a; border-radius: 2px; pointer-events: none; z-index: 100; }

.mermaid svg { color: rgb$46, 46, 46$; font: normal normal 400 normal 13px / 20.8px Menlo, "DejaVu Sans Mono", "Liberation Mono", Consolas, "Ubuntu Mono", "Courier New", "andale mono", "lucida console", monospace; } ABCDgraph TD; A--&gt;B; A--&gt;C; B--&gt;D; C--&gt;D; For details see the Mermaid official page.

Standard Markdown

Headers

## H1

### H2

#### H3

**H4**

**H5**

**H6**

Alternatively, for H1 and H2, an underline-ish style:

## Alt-H1

### Alt-H2

Header IDs and links

All Markdown-rendered headers automatically get IDs, except in comments.

On hover a link to those IDs becomes visible to make it easier to copy the link to the header to give it to someone else.

The IDs are generated from the content of the header according to the following rules:

All text is converted to lowercase All non-word text $e.g., punctuation, HTML$ is removed All spaces are converted to hyphens Two or more hyphens in a row are converted to one If a header with the same ID has already been generated, a unique incrementing number is appended, starting at 1.

For example:

## This header has spaces in it

### This header has a :thumbsup: in it

## This header has Unicode in it: 한글

### This header has spaces in it

#### This header has spaces in it

Would generate the following link IDs:

this-header-has-spaces-in-it this-header-has-a-in-it this-header-has-unicode-in-it-한글 this-header-has-spaces-in-it this-header-has-spaces-in-it-1

Note that the Emoji processing happens before the header IDs are generated, so the Emoji is converted to an image which then gets removed from the ID.

Emphasis

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.~~ 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.

Lists

1. First ordered list item
2. Another item
   * Unordered sub-list.
3. Actual numbers don't matter, just that it's a number
   1. Ordered sub-list
4. And another item.
5. Unordered list can use asterisks
6. Or minuses
7. Or pluses

First ordered list item Another item

Unordered sub-list.

Actual numbers don't matter, just that it's a number

Ordered sub-list

And another item.

Unordered list can use asterisks Or minuses Or pluses

If a list item contains multiple paragraphs, each subsequent paragraph should be indented with four spaces.

1. First ordered list item

Second paragraph of first item.

2. Another item

First ordered list item

Second paragraph of first item.

Another item

If the second paragraph isn't indented with four spaces, the second list item will be incorrectly labeled as 1.

1. First ordered list item

Second paragraph of first item.

2. Another item

First ordered list item

Second paragraph of first item.

Another item

Links

There are two ways to create links, inline-style and reference-style.

[I'm an inline-style link](https://www.google.com)

[I'm a reference-style link](https://www.mozilla.org)

[I'm a relative reference to a repository file](LICENSE)

[I am an absolute reference within the repository](/doc/user/markdown.md)

[I link to the Milestones page](/../milestones)

[You can use numbers for reference-style link definitions](http://slashdot.org)

Or leave it empty and use the [link text itself](https://www.reddit.com)

Some text to show that the reference links can follow later.

Note: Relative links do not allow referencing project files in a wiki page or wiki page in a project file. The reason for this is that, in GitLab, wiki is always a separate Git repository. For example, [I'm a reference-style link](style) will point the link to wikis/style when the link is inside of a wiki markdown file.

Images

Here's our logo $hover to see the title text$:

Inline-style:

Reference-style:

Here's our logo:

Inline-style:

Reference-style:

Blockquotes

> 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.

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.

See the documentation for HTML::Pipeline's SanitizationFilter class for the list of allowed HTML tags and attributes. In addition to the default SanitizationFilter whitelist, GitLab allows span, abbr, details and summary elements.

Definition listIs something people use sometimes.Markdown in HTMLDoes \*not\* work \*\*very\*\* well. Use HTML _tags_.

Definition list Is something people use sometimes.

Markdown in HTML Does _not_ work **very** well. Use HTML tags.

Details and Summary

Content can be collapsed using HTML's  and  tags. This is especially useful for collapsing long logs so they take up less screen space.

Click me to collapse/fold. These details will remain hidden until expanded.

PASTE LOGS HERE

Note: Unfortunately Markdown is not supported inside these tags, as described by the markdown specification. You can work around this by using HTML, for example you can use  tags instead of code fences.

Click me to collapse/fold. These details will remain hidden until expanded.

```text
PASTE LOGS HERE
```

Horizontal Rule

Three or more...

Hyphens

Asterisks

Underscores Three or more...

Hyphens

Asterisks

Underscores

Line Breaks

My basic recommendation for learning how line breaks work is to experiment and discover -- hit  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:

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 _does not break_ and just follows the previous line in the _same paragraph_.

This line is also a separate paragraph, and...  
This line is _on its own line_, because the previous line ends with two spaces. $but still in the _same paragraph_$

spaces. 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 does not break and just follows the previous line in the same paragraph.

This line is also a separate paragraph, and... This line is on its own line, because the previous line ends with two spaces. $but still in the same paragraph$

spaces.

Tables

Tables aren't part of the core Markdown spec, but they are part of GFM and Markdown Here supports them.

| header 1 | header 2 |
| --- | --- |
| cell 1 | cell 2 |
| cell 3 | cell 4 |

Code above produces next output:

header 1 header 2

cell 1 cell 2

cell 3 cell 4

Note

The row of dashes between the table header and body must have at least three dashes in each column.

By including colons in the header row, you can align the text within that column:

| Left Aligned | Centered | Right Aligned | Left Aligned | Centered | Right Aligned |
| :--- | :---: | ---: | :--- | :---: | ---: |
| Cell 1 | Cell 2 | Cell 3 | Cell 4 | Cell 5 | Cell 6 |
| Cell 7 | Cell 8 | Cell 9 | Cell 10 | Cell 11 | Cell 12 |

Left Aligned Centered Right Aligned Left Aligned Centered Right Aligned

Cell 1 Cell 2 Cell 3 Cell 4 Cell 5 Cell 6

Cell 7 Cell 8 Cell 9 Cell 10 Cell 11 Cell 12

Footnotes

You can add footnotes to your text as follows. : This is my awesome footnote. You can add footnotes to your text as follows.1

Wiki-specific Markdown

The following examples show how links inside wikis behave.

Wiki - Direct page link

A link which just includes the slug for a page will point to that page, at the base level of the wiki.

This snippet would link to a documentation page at the root of your wiki:

[Link to Documentation](documentation)

Wiki - Direct file link

Links with a file extension point to that file, relative to the current page.

If this snippet was placed on a page at /documentation/related, it would link to /documentation/file.md:

[Link to File]

Wiki - Hierarchical link

A link can be constructed relative to the current wiki page using ./, ../, etc.

If this snippet was placed on a page at /documentation/main, it would link to /documentation/related:

[Link to Related Page](./related)

If this snippet was placed on a page at /documentation/related/content, it would link to /documentation/main:

[Link to Related Page](../main)

If this snippet was placed on a page at /documentation/main, it would link to /documentation/related.md:

[Link to Related Page]

If this snippet was placed on a page at /documentation/related/content, it would link to /documentation/main.md:

[Link to Related Page]

Wiki - Root link

A link starting with a / is relative to the wiki root.

This snippet links to /documentation:

[Link to Related Page](/documentation)

This snippet links to /miscellaneous.md:

[Link to Related Page](/miscellaneous.md)

References

This document leveraged heavily from the Markdown-Cheatsheet. The Markdown Syntax Guide at Daring Fireball is an excellent resource for a detailed explanation of standard markdown.

Dillinger.io is a handy tool for testing standard markdown.