Welcome to the Volaire LARP Wiki syntax helper page. This guide will walk you through all supported DokuWiki formatting options so you can confidently create clear, consistent, and properly structured pages. Whether you're contributing rules, lore, or updates, this reference will help you stay on brand and in format.

📝 All content on the Volaire LARP Wiki is Out-of-Play (OOP) unless explicitly tagged as In-Play (IP).

• **Bold** → `bold`
• //Italic// → `italic`
• __Underline__ → `underline`
• ''Monospace'' → `monospace`
• ~~Strikethrough~~ → `strikethrough`
• Combined: **__//''Fancy''//__** → `Fancy`

Paragraphs are separated by a blank line.

Use \\ at the end of a line for a forced line break. Example: This is a sentence
with a break.

• http://example.com → http://example.com
• [[http://example.com|Visit site]] → Visit site

• [[operations:public:interactive_rulebook:start]]
• [[operations:public:core:magic|Magic & Spellcasting]]

Use colons : for namespaces.

• [[operations:public:start#navigation|Jump to Navigation]]

Unordered:

• * Item
• * Nested item

Ordered:

• - First
• - Sub-item

• ====== Main Title ======
• ===== Section =====
• ==== Subsection ====

A Table of Contents (TOC) is auto-generated with 3+ headings. Disable it using ~~NOTOC~~.

Add horizontal rules using four dashes: ----

Inline Image:

• {{namespace:image.png}}

Resize:

• {{namespace:image.png?200x100}}

Align:

• {{ namespace:image.png }} (centered)
• {{image.png }} (right-aligned)

Image Links:

• [[http://example.com|{{image.png}}]]

Syntax:

  ^ Header A ^ Header B ^
  | Row 1 A  | Row 1 B  |
  | Row 2 A  | Row 2 B  |

Advanced:

• || = colspan
• ::: = rowspan
• Align with spaces inside cells:

    | Left     |  Centered  |     Right |

• Inline:

This is %%''monospaced''%%

This is ''monospaced''

• Multiline:

<code>
Your code here
</code>

• With syntax highlighting:

<code python>
def cast_spell():
return "Fireball!"
</code>

def cast_spell():
    return "Fireball!"

Footnote:

• ((This is a footnote)) ¹⁾

Quoting:

> This is a response  
>> Nested response  

This is a response

Nested response

• Don't rely on heading-based section links—they can break if the title changes.
• Use internal links to connect relevant rules and lore.
• No CamelCase linking—DokuWiki does not auto-link those.
• Be consistent with formatting—it helps readers (and staff)!

Navigation: Return to Wiki Home | Interactive Rulebook Hub