meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
wiki:syntax [2026/09/03 00:23] – created - external edit 127.0.0.1wiki:syntax [2026/09/30 08:13] (current) – [**Dokuwiki Syntax**] tmh
Line 1: Line 1:
 ====== Formatting Syntax ====== ====== Formatting Syntax ======
 +
 +# Markdown
 +
 +This is intended as a quick reference and showcase. For more complete info, see [John Gruber's original spec](http://daringfireball.net/projects/markdown/) and the [Github-flavored Markdown info page](http://github.github.com/github-flavored-markdown/).
 +
 +This guide is adapted with some changes from https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet. It is adapted to match the featureset of DokuWiki more accurately.
 +
 +## Headers
 +
 +```no-highlight
 +# H1
 +## H2
 +### H3
 +#### H4
 +##### H5
 +###### H6
 +
 +```
 +
 +# H1
 +## H2
 +### H3
 +#### H4
 +##### H5
 +###### H6
 +
 +
 +## Emphasis
 +
 +```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.~~
 +```
 +
 +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
 +
 +(In this example, leading and trailing spaces are shown with with dots: ⋅)
 +
 +```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.
 +
 +⋅⋅⋅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.)
 +
 +* Unordered list can use asterisks
 +- Or minuses
 ++ Or pluses
 +```
 +
 +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.
 +
 +   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.)
 +
 +* 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 an inline-style link with title](https://www.google.com "Google's Homepage")
 +
 +[I'm a reference-style link][Arbitrary case-insensitive reference text]
 +
 +[I'm a relative reference to an eurogreen wiki page](..eurogreen_plus)
 +
 +[You can use numbers for reference-style link definitions][1]
 +
 +Or leave it empty and use the [link text itself].
 +
 +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).
 +```
 +
 +[I'm an inline-style link](https://www.google.com)
 +
 +[I'm an inline-style link with title](https://www.google.com "Google's Homepage")
 +
 +[I'm a reference-style link][Arbitrary case-insensitive reference text]
 +
 +[I'm a relative reference to an eurogreen wiki page](..eurogreen_plus)
 +
 +[You can use numbers for reference-style link definitions][1]
 +
 +Or leave it empty and use the [link text itself].
 +
 +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).
 +
 +
 +
 +## Images
 +
 +```no-highlight
 +Here's our logo (hover to see the title text):
 +
 +Inline-style: 
 +![alt text](https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 1")
 +
 +```
 +
 +Here's our logo (hover to see the title text):
 +
 +Inline-style: 
 +![alt text](https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 1")
 +
 +
 +## Code and Syntax Highlighting
 +
 +Code blocks are part of the Markdown spec, but syntax highlighting isn't. However, many renderers -- like Github's and *Markdown Here* -- support syntax highlighting. Which languages are supported and how those language names should be written will vary from renderer to renderer. *Markdown Here* supports highlighting for dozens of languages (and not-really-languages, like diffs and HTTP headers); to see the complete list, and how to write the language names, see the [highlight.js demo page](https://highlightjs.org/demo).
 +
 +```no-highlight
 +Inline `code` has `back-ticks around` it.
 +```
 +
 +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 &lt;b&gt;tag&lt;/b&gt;.
 +```
 +</code>
 +
 +
 +
 +```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>.
 +```
 +
 +
 +
 +## Footnotes
 +
 +Footnotes aren't part of the core Markdown spec, but they [supported by GFM](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes).
 +
 +```no-highlight
 +Here is a simple footnote[^1].
 +
 +A footnote can also have multiple lines[^2].  
 +
 +You can also use words, to fit your writing style more closely[^note].
 +
 +[^1]: My reference.
 +[^2]: Every new line should be prefixed with 2 spaces.  
 +  This allows you to have a footnote with multiple lines.
 +[^note]:
 +    Named footnotes will still render with numbers instead of the text but allow easier identification and linking.  
 +    This footnote also has been made with a different syntax using 4 spaces for new lines.
 +```
 +
 +Renders to:
 +
 +![rendered footnotes](https://user-images.githubusercontent.com/425687/160298620-6046b90e-698c-43cb-8e00-5f5871a906ad.png)
 +
 +
 +## Tables
 +
 +Tables aren't part of the core Markdown spec, but they are part of GFM and *Markdown Here* supports them. They are an easy way of adding tables to your email -- a task that would otherwise require copy-pasting from another application.
 +
 +```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 |
 +
 +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
 +```
 +
 +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 |
 +
 +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
 +
 +```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 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. 
 +
 +
 +## 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 &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:
 +
 +```
 +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*.
 +```
 +
 +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.)
 +
 +
 +---
 +
 +License: [CC-BY](https://creativecommons.org/licenses/by/3.0/)
 +
 +====== Dokuwiki Syntax ======
 +
  
 [[doku>DokuWiki]] supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing "Edit this page". If you want to try something, just use the [[playground:playground|playground]] page. The simpler markup is easily accessible via [[doku>toolbar|quickbuttons]], too. [[doku>DokuWiki]] supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing "Edit this page". If you want to try something, just use the [[playground:playground|playground]] page. The simpler markup is easily accessible via [[doku>toolbar|quickbuttons]], too.