Markdown¶
Il formato Markdown รจ stato creato in contrapposizione al markup dell'HTML. Qui la base รจ testo semplice con pochissime convenzioni che permettono al contenuto di essere poi convertito nei formati piรน utili (html, doc, pdf, ePub) garantendo un versioning perfetto e una preservazione e portabilitร ottimali
GitHub ha determinato massicciamente l'adozione dello standard Markdown per la documentazione e la scrittura in generale e ormai moltissimi siti vengono generati con Static Site Generators (vedi Jekyll o Hugo) a partire da contenuti scritti in Markdown, e la maggior parte degli editor di testo lo supportano nativamente.
Playground¶
guadare il codice di questa pagina per capire
note: GitHub ha una sua versione di MarkDown: https://github.github.com/gfm/
Heading 3¶
Text under Heading 3
Heading 4¶
Text under Heading 4
Heading 5¶
Text under Heading 5
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.
Highlights this part of text. And keywords
.
Emojis¶
๐คฃ ๐คฃ
Links¶
External links
- - www.google.com
- www.google.com with title
URLs and URLs in angle brackets will automatically get turned into links. http://www.example.com or http://www.example.com and sometimes example.com (but not on Github, for example).
Internal links
This links to the Introduction
Code¶
We can highlight a single keyword
or code blocks:
10 PRINT "generic code block"
20 GOTO 10
class myClasse {
}
here we can write code.
or **strong** test
Definitions¶
- Parola da definire
- รจ una cosa che si fa e non si dice
- Una seconda parola
- qui definiamo un'altro termine
List¶
- First ordered list item
- Another item
- Another item
- Another item
- Unordered sub-list.
- Unordered sub-list.
- Unordered sub-list.
- Actual numbers don't matter, just that it's a number
- Ordered sub-list
- Ordered sub-list
- Ordered sub-list
- the last item. You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
To have a line break without a paragraph, you will need to use two trailing spaces.
Note that this line is separate, but within the same paragraph.
(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
Images¶
Save your image (jpg or png format only) to img/
and insert it like this:
Tables¶
We can have nice tables.
Colons can be used to align columns.
colonna | colonna 2 |
---|---|
valore | calore 2 |
Tables | Are | Cool |
---|---|---|
col 3 is | right-aligned | $1600 |
col 2 is | centered | $12 |
zebra stripes | are neat | $1 |
Table: Table captions are done like this.
There must be at least 3 dashes separating each header cell. 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¶
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.
Maths¶
$$ y = -2.2x + 0.5 $$
$a+b= \frac{c}{c}$ $$a+b= \frac{c}{c}$$
$\lim{n \to \infty} x^{n+9}$ $$\lim{n \to \infty} x^{n+9}$$
$$\begin{aligned} a+b &= c \ b &= c - a \ 1 &= \frac{b}{c-a} \ \end{aligned}$$
Footnotes¶
Footnotes are best placed right after the paragraph first used.1
If you want to use endnotes instead turn them on in document options.
Comments¶
We can have comments in the text
Approfondimenti¶
- dal creatore di Markdown: https://daringfireball.net/projects/markdown/syntax
- Jekyll รจ il rendering engine delle GitHub pages: https://jekyllrb.com
- corso markdown: https://lab.github.com/githubtraining/communicating-using-markdown
-
But you can also put them at the end of the document. ↩