The Wiki: Three Spaces, One Editor

Longform pages with real-time co-editing and block-level secrets, in three spaces: your world reference, your table's shared notes, each player's journal.

The database holds your world's facts; the wiki holds its prose: histories, handouts, house rules, session journals. It is a block editor with live collaboration, and since Grimoire 1.5 it is three wikis, not one.

The three spaces

The three wiki spaces: the Campaign wiki the GM writes, the Party wiki everyone writes, and one Player wiki per member shared only with the GM. Campaign Your world's reference. You write it. Players read what visibility allows. Visibility tiers apply Player editing: GM toggle Party The table's shared space. Everyone reads and writes: session notes, loot splits, theories, plans. No tiers. All members see all Player One per member. Your character journal and private notes. Visible to you and your GM, never to other players GMs switch spaces with the tab rail above the wiki. Players see all three stacked in the portal sidebar.
Every campaign gets all three. As the GM you switch spaces with the tab rail above the page tree.
  • The Campaign wiki is your world reference. You write it; players read what visibility allows. Players cannot edit it unless you flip the "players can edit the campaign wiki" toggle under Settings → Player Portal.
  • The Party wiki belongs to the whole table. Everyone reads and writes; there are no visibility tiers because there is nothing to hide from each other. Session notes, plans, loot ledgers, theories.
  • Each member gets a Player wiki of their own, and the interface tells them plainly who sees it: the player and you, never other players. Character journals live here.

Writing with blocks

Every page is a stack of blocks: paragraphs, headings, lists, quotes, callouts, images, dividers, and nested pages. Type / on an empty line to insert one:

CommandBlock
/h1 /h2 /h3Headings
/bullet, /numberedLists
/quote, /calloutQuote and callout boxes
/image, /mediaImages, image beside text
/dividerHorizontal rule
/pageA nested child page

Formatting works the way you expect: Ctrl B bold, Ctrl I italic, Ctrl E code, or plain markdown (**bold**, # heading, - lists) as you type; select text for the floating toolbar with links and more. Grab the six-dot handle to reorder blocks, and type @ to link an entity inline.

Saving

There is no Save button. Changes persist continuously; a status pill in the header tells you where things stand, and Ctrl S forces an immediate flush if you are about to close your laptop mid-sentence.

Collaboration is live: everyone on a page sees everyone else's cursors and edits as they happen, presence avatars show who is here (an amber badge marks the GM), and nobody ever overwrites anybody. Undo affects your changes, not your co-writers'.

Organizing pages

  • Pages nest. Drag them in the page tree to restructure; /page creates a child right from the editor.
  • Every space has an indelible Home page as its root.
  • Deleted pages go to the Trash at the bottom of the page tree, and can be restored from there.

The right rail of every page carries its table of contents and the entities mentioned on it, each one a click away from the full record.

Finding things

Wiki search covers titles and page text. From anywhere, the palette's (Ctrl K) wiki mode searches every page you can read; players have the same power in the portal over the pages visible to them.

Secrets, block by block

In the campaign wiki, visibility applies per block, not just per page. A location's public history and the truth of what happened there can sit in adjacent paragraphs, one readable by your table, one by you alone:

  • Common Knowledge: everyone
  • Player Knowledge: what the party has learned
  • GM Secret: you only
  • Inherit: follow the page's own tier, the default

Hover a block and set its tier from the toolbar. Pages themselves carry a tier too, so a wholly secret page is one setting, not fifty. Preview as Player in the page header shows you exactly what your table will see before they see it.

Players with read access get a genuinely read-only page: no handles, no menus, no empty-block prompts, just the content.