Version 0.1
The «dizmo devdoc» help updater uses Pandoc as its markdown to html converter. Pandoc supports a rather wide range of extensions to the original markdown syntax. Have a look at its markdown syntax documentation.
This document has been created to test and show the possibilities of the Pandoc markdown syntax extensions.
strong or strong
emphasize or emphasize ( Cmd + I )
Sometimes I want a lot of text to be bold. Like, seriously, a LOT of text
Right angle brackets > are used for block quotes.
This is a block quote. This paragraph has two lines.
- This is a list inside a block quote.
- Second item.
Here is a “lazy” form, which requires the > character only on the first line of each block, is also allowed
This is a «lazy» block quote. This paragraph has two lines.
- This is a list inside a block quote.
- Second item.
Among the block elements that can be contained in a block quote are other block quotes. That is, block quotes can be nested:
This is a block quote.
A block quote within a block quote.
Inline code are surround by backtick
key.
Start with a line containing 3 or more backticks, and ends with the first line with the same number of backticks
Fenced code blocks are like Stardard Markdown’s regular code
blocks, except that they’re not indented and instead rely on
a start and end fence lines to delimit the code block.
Tilde works too
if (a > 3) {
moveShip(5 * gravity, DOWN);
}
… or alternatively use indented code blocks by indenting text by at least 4 spaces or a tab
Indent each line by at least 1 tab, or 4 spaces.
var Mou = exactlyTheAppIwant;
100 101 102 |
|
10 11 12 13 |
|
var pw = viewer.privateStorage.getProperty("login/password");
dizmo.publicStorage.setProperty("stdout/topNumbers", [25, 3.14, 9, 7.222]);
bundle.privateStorage.deleteProperty("oldItem");
var subId = otherDizmo.publicStorage.subscribeToProperty("stdout/time/start", handleStartTime(changedValues), {recursive:true});
An email example@example.com link.
An email example@example.com link.
Simple inline link http://chenluois.com, another inline link Smaller, one more inline link with title Resize.
A reference style link. Input id, then anywhere in the doc, define the link with corresponding id:
Titles ( or called tool tips ) in the links are optional.
An inline image , title is optional.
A reference style image.
Ordered lists are created using "1." + Space:
Unordered list are created using "*" + Space:
Or using "-" + Space:
End a line with two or more spaces will create a hard linebreak, called <br />
in HTML.
Above line ended with 2 spaces.
Three or more asterisks or dashes:
Setext-style:
atx-style:
Header formatting:
Note that pandoc automatically adds anchor definitions for all headers you create (try the link)
Footnotes work mostly like reference-style links. A footnote is made of two things: a marker in the text that will become a superscript number; a footnote definition that will be placed in a list of footnotes at the end of the document. A footnote looks like this:
That's some text with a footnote.1
Wrap with 2 tilde characters:
Strikethrough
A simple table looks like this:
First Header | Second Header | Third Header |
---|---|---|
Content Cell | Content Cell | Content Cell |
Content Cell | Content Cell | Content Cell |
If you wish, you can add a leading and tailing pipe to each line of the table:
First Header | Second Header | Third Header |
---|---|---|
Content Cell | Content Cell | Content Cell |
Content Cell | Content Cell | Content Cell |
Specify alignment for each column by adding colons to separator lines:
First Header | Second Header | Third Header |
---|---|---|
Left | Center | Right |
Left | Center | Right |
Click the link to scroll to back to the Overview header.
And that's the footnote.↩