Formatierung Syntax

DokuWiki unterstützt einige einfachen Markup-Sprache, die versucht, die Datendateien so lesbar wie möglich zu machen. Diese Seite enthält alle möglichen Syntax, die Sie verwenden können, wenn die Seiten bearbeiten. Haben Sie einfach einen Blick auf den Quelltext dieser Seite drücken, „Diese Seite bearbeiten“. Wenn Sie etwas ausprobieren möchten, benutzen Sie einfach die Testseite. Das einfachere Markup ist auch über Quickbuttons, leicht zu erreichen.

Einfache Text-Formatierung

DokuWiki unterstützt fett, kursiv, unterstrichen und Code Schrift im Text. Natürlich kann man auch alles Kombinieren.

DokuWiki unterstützt **fett**, //kursiv//, __unterstrichen__ und ''Code Schrift'' im Text.
Natürlich kann man auch alles **__//'' Kombinieren''//__**.

Man kann tiefgestellt und hochgestellt schreiben.

Man kann <sub>tiefgestellt</sub> und <sup>hochgestellt</sup> schreiben.

Man kann auch etwas als gelöscht markieren.

Man kann auch etwas als <del>gelöscht</del> markieren.

Absätze werden aus leere Zeilen erstellt. Wenn Sie einen Zeilenumbruch ohne einen Absatz erzwingen möchten, können Sie zwei umgekehrte Schrägstriche, gefolgt von einem Leerzeichen oder das Ende der Linie.

Dies ist ein Text mit einigen Zeilenumbrüchen
beachte, dass die zwei umgekehrten Schrägstriche nur am Ende
erkannt werden, oder gefolgt von
einem Leerzeichen \\hier ist es ohne Leerzeichen.

Dies ist ein Text mit einigen Zeilenumbrüchen\\ beachte, dass die
zwei umgekehrten Schrägstriche nur am Ende\\ erkannt werden,
oder gefolgt von\\ einem Leerzeichen \\hier ist es ohne Leerzeichen.

Man sollten erzwungene Zeilenumbrüche nur verwenden, wenn sie wirklich nötig sind.

Texthintergrund farblich verändern (plugin)

Durch das Color Plugin ist es möglich Text in anderen Farben darzustellen.

text text text text FIXME

<color green>text</color> <color blue/lightgrey>text</color> 
<color #FF0000>text</color> <color /#FFff00>text</color>

xref Plugin zum formatieren von php

Dieses Plugin macht eine PHPXref generierte Dokumentation einfach verlinken. Sie können mit Funktionen, konstanten, Variablen, Klassen Tabellen und Dateinamen verknüpfen. Das Plugin wird herausfinden, was du gemeint hast automatisch. Die XRef Dokumentation muss auf dem gleichen Server wie der DokuWiki Installation mit diesem Plugin zur Verfügung.

Die Syntax ähnelt Interwiki-Links. Starte einfach den Link mit der Xref > Schlüsselwort gefolgt von einer Funktion, konstante, Variable, Klasse, Tabelle oder Datei Name.

Hier ein Beispiel:

  * A Funktion: [[xref>wl()]]
  * A Variable: [[xref>$USERINFO]]
  * A Class: [[xref>auth_basic]]
  * A Datei: [[xref>inc/auth.php]]
  * A Funktion mit einem Titel: [[xref>cleanID()|Dies ist eine wichtige Funktion]]

It looks like this:

Bootstrap Wrapper Plugin (plugin)

Jumbotron

<jumbotron>

Hallo, Welt!

Dies ist eine einfache Box im jumbotron-style als Komponente um zusätzliche Aufmerksamkeit auf besondere Inhalte oder Informationen zu erregen. </jumbotron>

  <jumbotron>
  == Hallo, Welt ==
  
  Dies ist eine einfache Box im jumbotron-style 
  als Komponente um zusätzliche Aufmerksamkeit auf besondere
  Inhalte oder Informationen zu erregen.
  </jumbotron>

Panel

<panel type=„default“ title=„Titel des Panel“ subtitle=„Untertitel“ icon=„fa fa-house“> Panel Inhaltestext </panel>

  <panel type="default" title="Titel des Panel" subtitle="Untertitel" icon="fa fa-house">
  Panel Inhaltestext
  </panel>

Alert

<alert type=„success“ icon=„glyphicon glyphicon-user“ dismiss=„true“> Gut gemacht! Diese wichtige Warnmeldung wird sicher gelesen </alert>

  <alert type="success" icon="glyphicon glyphicon-user" dismiss="true">
  **Gut gemacht!** Diese wichtige Warnmeldung wird sicher gelesen
  *</alert>

Text

* <text type=„muted“>muted</text>

* <text type=„primary“>Primäre</text>

* <text type=„success“>Erfolgreich</text>

* <text type=„info“>Info</text>

* <text type=„warning“>Warnung</text>

* <text type=„danger“>Gefährlich</text>

  * <text type="muted">muted</text>
  * <text type="primary">Primäre</text>
  * <text type="success">Erfolgreich</text>
  * <text type="info">Info</text>
  * <text type="warning">Warnung</text>
  * <text type="danger">Gefährlich</text>

Tooltip

<tooltip title=„Sample Text“ location=„bottom“>Lorem ipsum</tooltip> dolor sit amet…

<tooltip title="Sample Text" location="bottom">Lorem ipsum</tooltip> dolor sit amet...

Grids

<grid> <col sm=„6“>.col-sm-6</col> <col sm=„6“>.col-sm-6</col> </grid>

<grid>
<col sm="6">.col-sm-6</col>
<col sm="6">.col-sm-6</col>
</grid>

<grid> <col xs=„12“ sm=„6“ lg=„8“>.col-xs-12 .col-sm-6 .col-lg-8</col> <col xs=„6“ lg=„4“>.col-xs-6 .col-lg-4</col> </grid>

<grid>
<col xs="12" sm="6" lg="8">.col-xs-12 .col-sm-6 .col-lg-8</col>
<col xs="6" lg="4">.col-xs-6 .col-lg-4</col>
</grid>

Thumbnail

<grid> … <col xs=„6“ md=„3“> <thumbnail> </thumbnail> </col> … </grid>

<grid>
...
<col xs="6" md="3">
<thumbnail>
{{ wiki:dokuwiki-128.png }}
</thumbnail>
</col>
...
</grid>

<grid> … <col xs=„6“ md=„3“> <thumbnail> <caption>

DokuWiki

DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database. It is loved by users for its clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make DokuWiki especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki. </caption> </thumbnail> … </col> </grid>

<grid>
...
<col xs="6" md="3">
<thumbnail>
{{ wiki:dokuwiki-128.png }}
<caption>
=== DokuWiki ===

//DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database. It is loved by users for its clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make DokuWiki especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki.//
</caption>
</thumbnail>
...
</col>
</grid>

Well

<well>Look, I'm in a well!</well>

<well>Look, I'm in a well!</well>

Button

<button type=„success“ size=„lg“ icon=„glyphicon glyphicon-edit“>welcome</button>

<button type="success" size="lg" icon="glyphicon glyphicon-edit">[[:wiki:welcome]]</button>

<nav>

</nav>

<nav>
  * [[:start]]
  * [[:plugin:bootswrapper|Plugin]]
  * [[playground:playground]]
  * DokuWiki
    * [[:wiki:welcome]]
    * [[:wiki:syntax]]
</nav>

Configuration and Settings

Configuration Default
loadBootstrap 1
^ Configuration  ^ Default  ^
^ loadBootstrap  | 1        |

FIXME

DokuWiki unterstützt mehrere Möglichkeiten zum Erstellen von links.

DokuWiki unterstützt mehrere Möglichkeiten zum Erstellen von Links. Externe Links können einfach so: http://www.google.de oder so www.google.com geschrieben werden - Man kann auch den Link-Text: unabhängig vom Link schreiben. E-Mail-Adressen: < info@myxoops.org > werden automatisch formatiert und können direkt vom Email-Client aufgerufen werden.

DokuWiki unterstützt mehrere Möglichkeiten zum Erstellen von Links.
Externe Links können einfach so: http://www.google.de oder so www.google.com geschrieben werden
Man kann auch den Link-Text: [[http://www.google.de | unabhängig vom]] Link schreiben.
E-Mail-Adressen: < info@myxoops.org > werden automatisch formatiert und können direkt vom
Email-Client aufgerufen werden.

Interne Links werden mit eckigen Klammern erstellt. Man kann entweder nur geben ein Seitenname oder einen Seitenname mit zusätzlichen Text verwenden.

Interne Links werden mit eckigen Klammern erstellt. Man kann entweder nur geben ein [[Seitenname]] oder 
einen Seitenname [[Seitenname | mit zusätzlichen Text]] verwenden.

Wiki Seitennamen werden automatisch in Kleinbuchstaben konvertiert. Sonderzeichen sind nicht erlaubt.

[[doku>seitenname|Wiki Seitennamen]] werden automatisch in Kleinbuchstaben konvertiert.
Sonderzeichen sind nicht erlaubt.

Man kann auch eigene Namensräume verwenden, mit einem Doppelpunkt zwischen den Seitennamen.

Man kann auch [[eigene:Namensräume]] verwenden, mit einem Doppelpunkt zwischen den Seitennamen.

Details über Namensräume finden man unter namespaces.

Verknüpfung zu einem bestimmten Abschnitt sind ebenfalls möglich. Füge einfach den Namen des Abschnitts hinter dem Gartenzaunzeichen (Hash-Zeichen) ein. Dies verknüpft mit in diesem Abschnitt.

Dieser Link nach [[syntax#Interne Links|in diesem Abschnitt]].

Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section.

This links to [[syntax#internal|this Section]].

Bemerkung:

  • Links zu vorhandenen Seiten sehen anders aus als Links zu nicht existierenden Seiten.
  • DokuWiki verwendet keine Höckerschrift-Links standardmäßig. Wie man dies automatisch erstellen kann, wird in der de:config Datei eingestellt.
    Hinweis: Wenn DokuWiki ein Link ist, ist es aktiviert.
  • Wenn eine Abschnittsüberschrift geändert wird, verändert sich auch seine Lesezeichen. Somit sollte man sich auf Abschnitt Verknüpfung nicht zu sehr verlassen.

Interwiki

DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: Wiki.

DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].

Windows Shares

Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate Intranet.

Windows Shares like [[\\server\share|this]] are recognized, too.

Notes:

  • For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the „local zone“).
  • For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in conf/lang/en/lang.php (more details at localization):
    conf/lang/en/lang.php
    <?php
    /**
     * Customization of the english language file
     * Copy only the strings that needs to be modified
     */
    $lang['js']['nosmblinks'] = '';

You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this:

[[http://php.net|{{wiki:dokuwiki-128.png}}]]

Please note: The image formatting is the only formatting syntax accepted in link names.

The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links).

Footnotes

You can add footnotes 1) by using double parentheses.

You can add footnotes ((This is a footnote)) by using double parentheses.

Sectioning

You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string ~~NOTOC~~ in the document.

Headline Level 3

Headline Level 4

Headline Level 5
==== Headline Level 3 ====
=== Headline Level 4 ===
== Headline Level 5 ==

By using four or more dashes, you can make a horizontal line:


Media Files

You can include external and internal images, videos and audio files with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height2):

Resized external image:

Real size:                        {{wiki:dokuwiki-128.png}}
Resize to given width:            {{wiki:dokuwiki-128.png?50}}
Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
Resized external image:           {{http://php.net/images/php.gif?200x50}}

By using left or right whitespaces you can choose the alignment.

{{ wiki:dokuwiki-128.png}}
{{wiki:dokuwiki-128.png }}
{{ wiki:dokuwiki-128.png }}

Of course, you can add a title (displayed as a tooltip by most browsers), too.

This is the caption

{{ wiki:dokuwiki-128.png |This is the caption}}

For linking an image to another page see Image Links above.

Supported Media Formats

DokuWiki can embed the following media formats directly.

Image gif, jpg, png
Video webm, ogv, mp4
Audio ogg, mp3, wav
Flash swf

If you specify a filename that is not a supported media format, then it will be displayed as a link instead.

By adding ?linkonly you provide a link to the media without displaying it inline

{{wiki:dokuwiki-128.png?linkonly}}

dokuwiki-128.png This is just a link to the image.

Fallback Formats

Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility.

For example consider this embedded mp4 video:

{{video.mp4|A funny video}}

When you upload a video.webm and video.ogv next to the referenced video.mp4, DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser.

Additionally DokuWiki supports a „poster“ image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a video.jpg file would work.

Lists

Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a * for unordered lists or a - for ordered ones.

  • This is a list
  • The second item
    • You may have different levels
  • Another item
  1. The same list but ordered
  2. Another item
    1. Just use indention for deeper levels
  3. That's it
  * This is a list
  * The second item
    * You may have different levels
  * Another item

  - The same list but ordered
  - Another item
    - Just use indention for deeper levels
  - That's it

Also take a look at the FAQ on list items.

Text Conversions

DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML.

The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well.

Text to Image Conversions

DokuWiki converts commonly used emoticons to their graphical equivalents. Those Smileys and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki:

  • 8-) 8-)
  • 8-O 8-O
  • :-( :-(
  • :-) :-)
  • =) =)
  • :-/ :-/
  • :-\ :-\
  • :-? :-?
  • :-D :-D
  • :-P :-P
  • :-O :-O
  • :-X :-X
  • :-| :-|
  • ;-) ;-)
  • ^_^ ^_^
  • :?: :?:
  • :!: :!:
  • LOL LOL
  • FIXME FIXME
  • DELETEME DELETEME

Text to HTML Conversions

Typography: DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.

→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ® „He thought 'It's a man's world'…“

-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
"He thought 'It's a man's world'..."

The same can be done to produce any kind of HTML, it just needs to be added to the pattern file.

There are three exceptions which do not come from that pattern file: multiplication entity (640×480), 'single' and „double quotes“. They can be turned off through a config option.

Quoting

Some times you want to mark some text to show it's a reply or comment. You can use the following syntax:

I think we should do it

> No we shouldn't

>> Well, I say we should

> Really?

>> Yes!

>>> Then lets do it!

I think we should do it

No we shouldn't
Well, I say we should
Really?
Yes!
Then lets do it!

Tables

DokuWiki supports a simple syntax to create tables.

Heading 1 Heading 2 Heading 3
Row 1 Col 1 Row 1 Col 2 Row 1 Col 3
Row 2 Col 1 some colspan (note the double pipe)
Row 3 Col 1 Row 3 Col 2 Row 3 Col 3

Table rows have to start and end with a | for normal rows or a ^ for headers.

^ Heading 1      ^ Heading 2       ^ Heading 3          ^
| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
| Row 2 Col 1    | some colspan (note the double pipe) ||
| Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |

To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!

Vertical tableheaders are possible, too.

Heading 1 Heading 2
Heading 3 Row 1 Col 2 Row 1 Col 3
Heading 4 no colspan this time
Heading 5 Row 2 Col 2 Row 2 Col 3

As you can see, it's the cell separator before a cell which decides about the formatting:

|              ^ Heading 1            ^ Heading 2          ^
^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
^ Heading 4    | no colspan this time |                    |
^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |

You can have rowspans (vertically connected cells) by adding ::: into the cells below the one to which they should connect.

Heading 1 Heading 2 Heading 3
Row 1 Col 1 this cell spans vertically Row 1 Col 3
Row 2 Col 1 Row 2 Col 3
Row 3 Col 1 Row 2 Col 3

Apart from the rowspan syntax those cells should not contain anything else.

^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
| Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
| Row 2 Col 1    | :::                        | Row 2 Col 3        |
| Row 3 Col 1    | :::                        | Row 2 Col 3        |

You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.

Table with alignment
right center left
left right center
xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx

This is how it looks in the source:

^           Table with alignment           ^^^
|         right|    center    |left          |
|left          |         right|    center    |
| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |

Note: Vertical alignment is not supported.

No Formatting

If you need to display text exactly like it is typed (without any formatting), enclose the area either with <nowiki> tags or even simpler, with double percent signs %%.

This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it. The same is true for //__this__ text// with a smiley ;-).

<nowiki>
This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
</nowiki>
The same is true for %%//__this__ text// with a smiley ;-)%%.

Code Blocks

You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags <code> or <file>.

This is text is indented by two spaces.
This is preformatted code all spaces are preserved: like              <-this
This is pretty much the same, but you could use it to show that you quoted a file.

Those blocks were created by this source:

  This is text is indented by two spaces.
<code>
This is preformatted code all spaces are preserved: like              <-this
</code>
<file>
This is pretty much the same, but you could use it to show that you quoted a file.
</file>

Syntax Highlighting

DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. <code java> or <file java>.

/**
 * The HelloWorldApp class implements an application that
 * simply displays "Hello World!" to the standard output.
 */
class HelloWorldApp {
    public static void main(String[] args) {
        System.out.println("Hello World!"); //Display the string.
    }
}

The following language strings are currently recognized: 4cs, 6502acme, 6502kickass, 6502tasm, 68000devpac, abap, actionscript-french, actionscript, actionscript3, ada, algol68, apache, applescript, asm, asp, autoconf, autohotkey, autoit, avisynth, awk, bascomavr, bash, basic4gl, bf, bibtex, blitzbasic, bnf, boo, c, c_loadrunner, c_mac, caddcl, cadlisp, cfdg, cfm, chaiscript, cil, clojure, cmake, cobol, coffeescript, cpp, cpp-qt, csharp, css, cuesheet, d, dcs, delphi, diff, div, dos, dot, e, epc, ecmascript, eiffel, email, erlang, euphoria, f1, falcon, fo, fortran, freebasic, fsharp, gambas, genero, genie, gdb, glsl, gml, gnuplot, go, groovy, gettext, gwbasic, haskell, hicest, hq9plus, html, html5, icon, idl, ini, inno, intercal, io, j, java5, java, javascript, jquery, kixtart, klonec, klonecpp, latex, lb, lisp, llvm, locobasic, logtalk, lolcode, lotusformulas, lotusscript, lscript, lsl2, lua, m68k, magiksf, make, mapbasic, matlab, mirc, modula2, modula3, mmix, mpasm, mxml, mysql, newlisp, nsis, oberon2, objc, objeck, ocaml-brief, ocaml, oobas, oracle8, oracle11, oxygene, oz, pascal, pcre, perl, perl6, per, pf, php-brief, php, pike, pic16, pixelbender, pli, plsql, postgresql, povray, powerbuilder, powershell, proftpd, progress, prolog, properties, providex, purebasic, pycon, python, q, qbasic, rails, rebol, reg, robots, rpmspec, rsplus, ruby, sas, scala, scheme, scilab, sdlbasic, smalltalk, smarty, sql, systemverilog, tcl, teraterm, text, thinbasic, tsql, typoscript, unicon, uscript, vala, vbnet, vb, verilog, vhdl, vim, visualfoxpro, visualprolog, whitespace, winbatch, whois, xbasic, xml, xorg_conf, xpp, yaml, z80, zxbasic

Downloadable Code Blocks

When you use the <code> or <file> syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this:

<file php myexample.php>
<?php echo "hello world!"; ?>
</file>
myexample.php
<?php echo "hello world!"; ?>

If you don't want any highlighting but want a downloadable file, specify a dash (-) as the language code: <code - myfile.foo>.

Embedding HTML and PHP

You can embed raw HTML or PHP code into your documents by using the <html> or <php> tags. (Use uppercase tags if you need to enclose block level elements.)

HTML example:

<html>
This is some <span style="color:red;font-size:150%;">inline HTML</span>
</html>
<HTML>
<p style="border:2px dashed red;">And this is some block HTML</p>
</HTML>

This is some <span style="color:red;font-size:150%;">inline HTML</span>

<p style="border:2px dashed red;">And this is some block HTML</p>

PHP example:

<php>
echo 'The PHP version: ';
echo phpversion();
echo ' (generated inline HTML)';
</php>
<PHP>
echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';
</PHP>

echo 'The PHP version: '; echo phpversion(); echo ' (inline HTML)';

echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';

Please Note: HTML and PHP embedding is disabled by default in the configuration. If disabled, the code is displayed instead of executed.

RSS/ATOM Feed Aggregation

DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, SimplePie is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:

Parameter Description
any number will be used as maximum number items to show, defaults to 8
reverse display the last items in the feed first
author show item authors names
date show item dates
description show the item description. If HTML is disabled all tags will be stripped
nosort do not sort the items in the feed
n[dhm] refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours).

The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. DokuWiki will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells DokuWiki to re-render the page if it is more than refresh period since the page was last rendered.

By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the reverse parameter, or display the feed as is with nosort.

Example:

{{rss>http://slashdot.org/index.rss 5 author date 1h }}

Control Macros

Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:

Macro Description
~~NOTOC~~ If this macro is found on the page, no table of contents will be created
~~NOCACHE~~ DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the <php> syntax above is used), adding this macro will force DokuWiki to rerender a page on every call

Syntax Plugins

DokuWiki's syntax can be extended by Plugins. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:

1) This is a footnote
2) when the aspect ratio of the given width and height doesn't match that of the image, it will be cropped to the new ratio before resizing
wiki/syntax.txt · Zuletzt geändert: 2016/09/21 15:53 von admin
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0