Skip to content

Wiki Conventions

Read this before creating or substantially editing a page. It defines the small, consistent set of conventions this wiki uses. Do not invent new frontmatter fields or section templates without a real need — consistency here is what keeps the wiki maintainable by future agents who haven't read every page.

Frontmatter schema

Every content page in Wiki/ and Campaigns/ should open with YAML frontmatter. Only include fields that apply; don't pad pages with empty fields.

---
type: character            # character | family | faction | location | event | item | creature | concept | timeline | meta
status: active              # active | deceased | historical | unknown | destroyed | disbanded (use whatever fits the type)
campaign: [Chrono Conundrum, Gods and Dragons]   # which campaign(s) this entity is relevant to
canon: [Played, Backstory, Planned, Bridge]       # canon classification(s) that apply to this page's content — see Canon and Continuity.md
                                                    # (also: Character Belief, Rumor / In-World Claim, Implied / Uncertain, Contradictory, GM Clarification — see CLAUDE.md §3)
aliases: [Other Name, Nickname, "Formal Title"]
tags: [tiefling, blood-hunter, windsor-family]
---

Notes: - campaign values: Chrono Conundrum (the original, completed campaign), Gods and Dragons (the current campaign), or both if the entity spans both. - canon is a list because a single page often mixes canon types (e.g. a character's early life is Backstory Canon, their session appearances are Played Canon, their fate is Planned Canon). Call out which sections are which in prose or a per-section note when it matters. - aliases is what powers Obsidian's alias-based linking and search — this is the primary duplicate-page defense. List every name, nickname, married name, or title a reader might search for. - Keep tags short and reusable (lowercase, hyphenated). Don't create a one-off tag for a single page.

  • Link naturally in prose: Laethan met [Daphne](../Wiki/Characters/Daphne Windsor.md) at the Millennium Fair.
  • Use the |display text pipe when the natural sentence needs different phrasing than the page title.
  • Prefer inline links over "See Also" dumps. A short "Related" list at the bottom is fine for things that don't fit naturally in prose, but don't let it become the primary way pages connect.
  • Before creating a new page, search for the entity under its known aliases. If in doubt, check Meta/Entity Registry.md.

Page sections

Don't force every page into an identical template — let the subject dictate the sections. As a loose guide:

Character pages commonly use: Overview, History (or Early Life / Academy Years / etc. as sub-sections), Personality, Family, Relationships, Role in the Original Campaign, Role in Gods and Dragons, Significant Events, Secrets / Hidden Information, Unresolved Threads, Sources.

Event pages commonly use: Overview, Participants, Location, Events, Consequences, Related Threads, Sources.

Location / Faction / Item / Creature pages: use whatever subset of Overview / History / Description / Notable Members / Notable Appearances / Sources fits. A one-paragraph location doesn't need six headings.

Every substantive page ends with a ## Sources section (see below).

Sources sections

List the actual source document(s) the page draws from, using the filename or an unambiguous short name for it — never a fabricated citation. Examples of correct citation style, drawn from what actually exists in Sources/:

## Sources
- Wolfgang Windsor Backstory.docx
- Chrono Conundrum Notes.md, Sessions 26–51
- Chrono_Conundrum_Ending_Outline.docx.md ("Chrono Conundrum — Ending Outline & Timeline — Final Draft")

Do not invent page numbers, session numbers, dates, chapter numbers, or quotations. If you can't pin down precisely which session something happened in, say "Chrono Conundrum Notes.md, session range unclear" rather than guessing a specific number.

Canon labeling in prose

When a claim's canon status matters to the reader (most often: is this actually settled, or just an outline/plan?), say so inline rather than leaving it ambiguous:

The Ending Outline (Planned Canon — never played) has Daphne sacrificing herself to banish Lavos.

versus

Trout brought down the Dread Gloom in Session 15 (Played Canon).

Handling contradictions

If two sources disagree (e.g. two different accounts of why Laethan was expelled), do not silently pick one. Present both, note the discrepancy inline if brief, and log it in Meta/Contradictions and Open Questions.md if it's significant enough to need tracking across pages.

What doesn't need its own page

Exercise judgment. A name mentioned once with no further significance (a random tavern bully, a one-line NPC) belongs inside the page where it's mentioned, not as a standalone stub. When in doubt, check Meta/Entity Registry.md — entities are listed there even if they don't yet warrant a full page, with a note on why.