Markdown is a easy-to-use markup language for writing and this document contains all supported markdown features.
- Markdown Syntax
Headings from h1
through h6
are constructed with a #
for each level:
# H1
## H2
### H3
#### H4
##### H5
###### H6
Alternatively you can use ATX headings:
H1
======
H2
------
Renders to:
Alternatively you can use underlines:
Just write normal text:
Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.
You can use multiple consecutive newline characters (\n
) to create extra spacing between sections in a markdown document. However, if you need to ensure that extra newlines are not collapsed, you can use as many HTML <br>
elements as you want.
Alternatively you can add two spaces spaces at the end of your paragraph to force a soft linebreak.
The HTML <hr>
element is for creating a "thematic break" between paragraph-level elements. In markdown, you can use of the following for this purpose:
___
: three consecutive underscores---
: three consecutive dashes***
: three consecutive asterisks
Renders to:
For emphasizing a snippet of text with a heavier font-weight.
The following snippet of text is rendered as bold text.
**rendered as bold text**
renders to:
rendered as bold text
For emphasizing a snippet of text with italics.
The following snippet of text is rendered as italicized text.
_rendered as italicized text_
renders to:
rendered as italicized text
In GFM you can do strickthroughs by wrapping the text with double tildes.
~~Strike through this text.~~
Which renders to:
Strike through this text.
Autolinks are absolute URIs and email addresses inside <
and >
. They are parsed as links, where the URI or email address itself is used as the link's label.
<http://foo.bar.baz>
Renders to:
URIs or email addresses that are not wrapped in angle brackets are not recognized as valid autolinks by markdown parsers.
[Assemble](http://assemble.io)
Renders to (hover over the link, there is no tooltip):
[Upstage](https://github.com/upstage/ "Visit Upstage!")
Renders to (hover over the link, there should be a tooltip):
Named anchors enable you to jump to the specified anchor point on the same page. For example, each of these chapters:
# Table of Contents
* [Chapter 1](#chapter-1)
* [Chapter 2](#chapter-2)
* [Chapter 3](#chapter-3)
will jump to these sections:
## Chapter 1
Content for chapter one.
## Chapter 2
Content for chapter one.
## Chapter 3 <a name="chapter-3"></a>
Content for chapter one.
Anchor placement
Note that placement of achors is arbitrary, you can put them anywhere you want, not just in headings. This makes adding cross-references easy when writing markdown.
Images have a similar syntax to links but include a preceding exclamation point.
![MarkText](https://raw.githubusercontent.com/marktext/marktext/develop/resources/icons/256x256/marktext.png)
or
![Alt text](hhttps://raw.githubusercontent.com/marktext/marktext/develop/resources/icons/256x256/marktext.png "MarkText logo")
Like links, Images also have a footnote style syntax
![Alt text][id]
With a reference later in the document defining the URL location:
[id]: https://raw.githubusercontent.com/marktext/marktext/develop/resources/icons/256x256/marktext.png "MarkText logo"
Used for defining a section of quoting text from another source, within your document.
To create a blockquote, use >
before any text you want to quote.
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante
Renders to:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer posuere erat a ante.
Blockquotes can also be nested:
> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue.
Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
>> Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor
odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
>>> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue.
Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
Renders to:
Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
A list of items in which the order of the items does not explicitly matter.
You may use any of the following symbols to denote bullets for each list item:
* valid bullet
- valid bullet
+ valid bullet
For example
+ Lorem ipsum dolor sit amet
+ Consectetur adipiscing elit
+ Integer molestie lorem at massa
+ Facilisis in pretium nisl aliquet
+ Nulla volutpat aliquam velit
- Phasellus iaculis neque
- Purus sodales ultricies
- Vestibulum laoreet porttitor sem
- Ac tristique libero volutpat at
+ Faucibus porta lacus fringilla vel
+ Aenean sit amet erat nunc
+ Eget porttitor lorem
Renders to:
- Lorem ipsum dolor sit amet
- Consectetur adipiscing elit
- Integer molestie lorem at massa
- Facilisis in pretium nisl aliquet
- Nulla volutpat aliquam velit
- Phasellus iaculis neque
- Purus sodales ultricies
- Vestibulum laoreet porttitor sem
- Ac tristique libero volutpat at
- Faucibus porta lacus fringilla vel
- Aenean sit amet erat nunc
- Eget porttitor lorem
A list of items in which the order of items does explicitly matter.
1. Lorem ipsum dolor sit amet
2. Consectetur adipiscing elit
3. Integer molestie lorem at massa
4. Facilisis in pretium nisl aliquet
5. Nulla volutpat aliquam velit
6. Faucibus porta lacus fringilla vel
7. Aenean sit amet erat nunc
8. Eget porttitor lorem
Renders to:
- Lorem ipsum dolor sit amet
- Consectetur adipiscing elit
- Integer molestie lorem at massa
- Facilisis in pretium nisl aliquet
- Nulla volutpat aliquam velit
- Faucibus porta lacus fringilla vel
- Aenean sit amet erat nunc
- Eget porttitor lorem
Sometimes lists change, and when they do it's a pain to re-order all of the numbers. Markdown solves this problem by allowing you to simply use 1.
before each item in the list.
For example:
1. Lorem ipsum dolor sit amet
1. Consectetur adipiscing elit
1. Integer molestie lorem at massa
1. Facilisis in pretium nisl aliquet
1. Nulla volutpat aliquam velit
1. Faucibus porta lacus fringilla vel
1. Aenean sit amet erat nunc
1. Eget porttitor lorem
Automatically re-numbers the items and renders to:
- Lorem ipsum dolor sit amet
- Consectetur adipiscing elit
- Integer molestie lorem at massa
- Facilisis in pretium nisl aliquet
- Nulla volutpat aliquam velit
- Faucibus porta lacus fringilla vel
- Aenean sit amet erat nunc
- Eget porttitor lorem
- [ ] Lorem ipsum dolor sit amet
- [ ] Consectetur adipiscing elit
- [ ] Integer molestie lorem at massa
Renders to:
- Lorem ipsum dolor sit amet
- Consectetur adipiscing elit
- Integer molestie lorem at massa
Links in todo lists
- [ ] [foo](#bar)
- [ ] [baz](#qux)
- [ ] [fez](#faz)
Renders to:
Tables are created by adding pipes as dividers between each cell, and by adding a line of dashes (also separated by bars) beneath the header (this line of dashes is required).
- pipes do not need to be vertically aligned.
- pipes on the left and right sides of the table are sometimes optional
- three or more dashes must be used for each cell in the separator row
Example:
| Option | Description |
| ------ | ----------- |
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
Renders to:
Option | Description |
---|---|
data | path to data files to supply the data that will be passed into templates. |
engine | engine to be used for processing templates. Handlebars is the default. |
ext | extension to be used for dest files. |
Center text in a column
To center the text in a column, add a colon to the left and right of the dashes in the row beneath the header.
| Option | Description |
| :-: | :-: |
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
Option | Description |
---|---|
data | path to data files to supply the data that will be passed into templates. |
engine | engine to be used for processing templates. Handlebars is the default. |
ext | extension to be used for dest files. |
Right-align the text in a column
To right-align the text in a column, add a colon to the right of the dashes in the row beneath the header.
| Option | Description |
| ------:| -----------:|
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
Renders to:
Option | Description |
---|---|
data | path to data files to supply the data that will be passed into templates. |
engine | engine to be used for processing templates. Handlebars is the default. |
ext | extension to be used for dest files. |
Wrap inline snippets of code with a single backtick: `
.
For example, to show <div></div>
inline with other text, just wrap it in backticks.
For example, to show `<div></div>` inline with other text, just wrap it in backticks.
Three consecutive backticks, referred to as "code fences", are used to denote multiple lines of code: ```
.
For example, this:
```html Example text here... ```
Appears like this when viewed in a browser:
Example text here...
You may also indent several lines of code by at least four spaces, but this is not recommended as it is harder to read, harder to maintain, and doesn't support syntax highlighting.
Example:
// Some comments
line 1 of code
line 2 of code
line 3 of code
// Some comments
line 1 of code
line 2 of code
line 3 of code
To activate the correct styling for the language inside the code block, simply add the file extension of the language you want to use directly after the first code "fence": ```js
, and syntax highlighting will automatically be applied in the rendered HTML (if supported by the parser). For example, to apply syntax highlighting to JavaScript code:
```js grunt.initConfig({ assemble: { options: { assets: 'docs/assets', data: 'src/data/*.{json,yml}', helpers: 'src/custom-helpers.js', partials: ['src/partials/**/*.{hbs,md}'] }, pages: { options: { layout: 'default.hbs' }, files: { './': ['src/templates/pages/index.hbs'] } } } }); ```
Which renders to:
grunt.initConfig({
assemble: {
options: {
assets: 'docs/assets',
data: 'src/data/*.{json,yml}',
helpers: 'src/custom-helpers.js',
partials: ['src/partials/**/*.{hbs,md}']
},
pages: {
options: {
layout: 'default.hbs'
},
files: {
'./': ['src/templates/pages/index.hbs']
}
}
}
});
Github-Flavored Markdown (GFM) allows you to highlight keyboard keys.
For example, this:
To copy, please press <kbd>CmdOrCtrl</kbd>+<kbd>C</kbd>
To paste, please press <kbd>CmdOrCtrl</kbd>+<kbd>V</kbd>
Which renders to:
To copy, please press CmdOrCtrl+C
To paste, please press CmdOrCtrl+V
Github-Flavored Markdown (GFM) supports also Emojis. 😍 😄 😂
To add an emojis, just surround the emoji name with colons, like this:
:heart: :zap: :cow: :dollar: :star: :tada:
Which renders to:
❤️ ⚡ 🐮 💵 ⭐ 🎉
NOTE: MarkText provides an emoji picker with search functionality.
Front matter allows you to insert metadata to your markdown document. The front matter block must be written in the first line before everything else, like in the examples below.
YAML front matter blocks are identified by an opening and closing ---
line.
---
title: YAML front matter example
key: value
---
Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus.
TOML front matter blocks are identified by an opening and closing +++
line.
+++
title = "YAML front matter example"
key = "value"
+++
Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus.
JSON front matter blocks are identified by an opening and closing ;;;
line or {
and }
.
{
"title": YAML front matter example
"key": {
"subkey1": "value 1",
"subkey2": "value 2"
}
}
Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus.
Wrap one line LaTeX with a single dollar sign: $
.
For example, to show $\alpha \beta \gamma$ inline with other text, just wrap it in dollar signs.
Two consecutive dollar signs are used to denote multiple lines of math formulas: $$
.
For example, this:
$$
R_x=\begin{pmatrix}
1 & 0 & 0 & 0\\
0 & cos(a) & -sin(a) & 0\\
0 & sin(a) & cos(a) & 0\\
0 & 0 & 0 & 1
\end{pmatrix}
$$
or
$$
m=\frac{b_y-a_y}{b_x-a_x}
$$
MarkText support class, flow chart, gantt and sequence diagrams powered by flowchart.js, mermaid and Vega-Lite. Code blocks with special language identifiers are used for diagrams.
For example, this:
## Vega-lite diagram Please see [introduction to Vega-Lite](https://vega.github.io/vega-lite/tutorials/getting_started.html) for details. ```vega-lite { "data": { "values": [ {"a": "C", "b": 2}, {"a": "C", "b": 7}, {"a": "C", "b": 4}, {"a": "D", "b": 1}, {"a": "D", "b": 2}, {"a": "D", "b": 6}, {"a": "E", "b": 8}, {"a": "E", "b": 4}, {"a": "E", "b": 7} ] }, "mark": "point", "encoding": { "x": {"field": "a", "type": "nominal"}, "y": {"field": "b", "type": "quantitative"} } } ``` ## Flowchart ```flowchart st=>start: Start|past e=>end: End|future op1=>operation: My Operation|past op2=>operation: Stuff|current sub1=>subroutine: My Subroutine|invalid cond=>condition: Yes or No?|approved:>http://www.google.com c2=>condition: Good idea|rejected io=>inputoutput: catch something...|future st->op1(right)->cond cond(yes, right)->c2 cond(no)->sub1(left)->op1 c2(yes)->io->e c2(no)->op2->e ``` ## Sequence diagram ```sequence Title: Here is a title A->B: Normal line B-->C: Dashed line C->>D: Open arrow D-->>A: Dashed open arrow ``` ## Flowchart ```mermaid graph TD; A-->B; A-->C; B-->D; C-->D; ``` ## Sequence diagram ```mermaid sequenceDiagram participant Alice participant Bob Alice->>John: Hello John, how are you? loop Healthcheck John->>John: Fight against hypochondria end Note right of John: Some note John-->>Alice: Great! John->>Bob: How about you? Bob-->>John: Jolly good! ``` ## Gantt diagram ```mermaid gantt dateFormat YYYY-MM-DD title Adding GANTT diagram to mermaid excludes weekdays 2014-01-10 section A section Completed task :done, des1, 2014-01-06,2014-01-08 Active task :active, des2, 2014-01-09, 3d Future task : des3, after des2, 5d Future task2 : des4, after des3, 5d ``` ## Class diagram (experimental) ```mermaid classDiagram Class01 <|-- AveryLongClass : Cool Class03 *-- Class04 Class05 o-- Class06 Class07 .. Class08 Class09 --> C2 : Where am i? Class09 --* C3 Class09 --|> Class07 Class07 : equals() Class07 : Object[] elementData Class01 : size() Class01 : int chimp Class01 : int gorilla Class08 <--> C2: Cool label ```
Please visit PlantUML website for more details.
@startuml
Alice -> Bob: Authentication Request
Bob --> Alice: Authentication Response
Alice -> Bob: Another authentication Request
Alice <-- Bob: Another authentication Response
@enduml
Any text between <
and >
that looks like an HTML tag will be parsed as a raw HTML tag and rendered to HTML without escaping.
Example:
**Visit <a href="https://github.com">Jon Schlinkert's GitHub Profile</a>.**
Renders to:
Visit Jon Schlinkert's GitHub Profile.
Any ASCII punctuation character may be escaped using a single backslash.
Example:
\*this is not italic*
Renders to:
*this is not italic*
This markdown cheatsheet was created by @jonschlinkert and modified. The source can be found here.