Campaigning Wiki

3 min read

Summary

Notes for shipping the Campaigning Wiki to each target platform — Obsidian/Quartz, MediaWiki, Notion — and what to adjust in the export.

Body

The wiki ships as plain Markdown with double-bracket wikilinks and YAML frontmatter. Only Wiki/ publishes; RAW/ stays private (already git-ignored via .gitignore). The same source tree can be adapted to each platform with minor transformations.

Obsidian / Quartz

  • Double-bracket wikilinks work as-is.

  • YAML frontmatter is parsed by Obsidian’s Dataview plugin, so the following queries build the equivalent of INDEX.md and by-tier.md automatically:

    TABLE status, tier, languages, categories
FROM "Wiki"
WHERE type = "article"
SORT slug ASC

  • Quartz (a static-site generator for Obsidian notes) needs no transformation; point it at Wiki/ as the content root.

  • Categories like strategy, organizing, digital map directly to Obsidian tags via tags: field — add if absent.

MediaWiki

  • Double-bracket wikilinks are roughly compatible (MediaWiki uses the same syntax). The wiki’s slugs are kebab-case (power-mapping) while MediaWiki titles are usually sentence-case; decide per project.
  • Strip YAML frontmatter; map each key to a MediaWiki template / category:
    • title: → page title (or use the filename)
    • status: → category (Category:Stub, Category:Emerging, Category:Established)
    • languages: → category (Category:Language/EN, …)
    • categories: → category (Category:Strategy, …)
    • tier: → category (Category:Core, …)
    • license: → category (Category:CC-attribution, Category:Link-only)
  • Run the wikilinks through a converter to flatten hyphens to spaces if you want Title Case.

Notion

  • Notion’s Markdown import is partial: double-bracket wikilinks are preserved as page mentions only if the target page already exists in the workspace.
  • Map each YAML key to a Notion database property: title → title, status → select, languages → multi-select, categories → multi-select, tier → select, license → select, updated → date.
  • Notion’s database view gives you filterable INDEX / by-language / by-category / by-tier for free.

GitHub Pages

  • Double-bracket wikilinks do not work on plain GitHub Pages; convert to relative Markdown links: [slug] → [power-mapping](power-mapping.md).
  • YAML frontmatter renders as visible text on GitHub Pages unless you use a static-site generator (Jekyll, Hugo, MkDocs) that consumes it.

What to adjust per platform

  • Wikilink syntax: works in Obsidian; needs conversion for MediaWiki / GitHub Pages / Notion.
  • Frontmatter: works in Obsidian; needs stripping / mapping elsewhere.
  • License metadata: always publish the license prominently. For link-only, add a footer note in CONVENTIONS.md reminding readers to check the source page.
  • RAW/: always keep private. Never commit or publish the RAW/ folder; it contains scraped content that may be copyright-encumbered even when our distilled pages are not.

Use it for

Planning an export; onboarding a downstream maintainer; choosing a host.

Open Questions

Graph View

Backlinks