Text Formatting Rules

Wikantik pages use CommonMark-flavored Markdown stored as .md files. The rendering engine is based on Flexmark, extended with Wikantik-specific syntax for plugins, access control, and metadata. Every page must start with a YAML frontmatter block for structured data.

I. Markdown Core

Wikantik supports standard CommonMark with the following active extensions:

ExtensionSyntax ExampleUse Case
Tables| Col | Col |GitHub-style pipe tables.
Footnotes[^1] and [^1]:Citations and side-notes.
DefinitionsTerm\n: DefStructural glossaries.
Attributes{.class}Appending CSS classes/IDs to blocks.
Math$E=mc^2$LaTeX-style inline and block math.

Headings

Use ATX-style headings (# through ######).

Code Blocks

Prefer fenced code blocks with language hints for syntax highlighting:

```java
public class HelloWorld { ... }
```

Mathematical Notation

II. Internal Linking and References

Internal links use standard Markdown syntax but resolve to page names (slugs) within the wiki:

Canonical IDs

Page slugs can change during refactoring. For permanent references in code, documentation, or runbooks, use the canonical_id.

III. Wikantik Bracket Syntax

Bracket syntax [{ ... }]() is used for dynamic functions and system controls.

FunctionSyntaxDescription
Plugins[{PluginName param=val}]()Execute a rendering plugin.
ACLs[{ALLOW view All}]()Define page-level permissions.
Variables[{$variableName}]()Inline a system or page variable.
Setters[{SET key=val}]()Define a page-scoped variable.

Access Control Lists (ACLs)

Place ACLs at the top of the file, before the first heading. Valid permissions include view, edit, modify, upload, rename, and delete.

IV. Core Plugins

Plugins extend the static Markdown with dynamic content.

V. Frontmatter Schema

The YAML frontmatter is the "Structural Spine" of the wiki.

---
canonical_id: 01H8G3... (Auto-injected on save)
title: Page Title
type: article | hub | runbook | design | reference
cluster: thematic-grouping
status: active | draft | deprecated
date: YYYY-MM-DD
summary: A one-sentence description.
tags: [tag1, tag2]
related: [PageSlug1, PageSlug2]
---

Type-Specific Requirements

Verification Metadata

Stamp pages as reviewed using the mark_page_verified tool or manual entry:

VI. Best Practices

  1. Summary Quality: Keep summaries between 50 and 160 characters. They drive search results and agent projections.
  2. No HTML: Wikantik escapes raw HTML by default for security. Use Markdown primitives or plugins for all styling.
  3. Frontmatter vs. Body: Store machine-queryable data (dates, types, relations) in frontmatter; store prose and examples in the body.