How to Build a D&D Campaign Wiki Your Whole Table Can Use

Most campaign wikis die before the third session.

A GM spends a weekend building an elaborate Notion workspace — linked databases, faction pages, NPC profiles. It's beautiful. Then they share the link with their players, two people open it, nobody navigates past the first page, and it quietly gets abandoned.

The problem isn't effort. It's architecture. A campaign wiki built for a GM's brain isn't built for a player's 90-second browse before game night.

Here's how to build one that actually gets used.

The Two Types of Campaign Wiki

Before you build anything, decide which type you need:

The GM Reference Wiki — Deep, detailed, private. Everything you know about the world, including things players haven't discovered yet. This is for you.

The Player-Facing Wiki — Curated, scannable, public to your table. Only what players actually need between sessions. This is for them.

Most GMs build one and call it both. That's why it fails. Players drown in lore they don't need, or GMs self-censor details that would actually be useful.

Build both. Keep them separate. This post is about the player-facing wiki — the one that gets used.

What Belongs in a Player-Facing Campaign Wiki

Rule of thumb: if a player would ask about it at the table, it belongs in the wiki.

🌍 World Overview (1 page, max)

The 30-second pitch for your world. Tone, setting, the central conflict. Not a history lesson — a vibe check. Players should finish reading it and immediately understand what kind of campaign this is.

👥 NPC Tracker

Not every NPC — just the ones the party has actually met. For each one:

• Name and role
• Where they last were
• How the party left things with them
• One thing players might want to remember

Update this after each session. Players will check it when they can't remember "wait, which one was Maren again?"

⚔️ Factions

A one-paragraph summary of each major faction. What they want, who they're allied with, who they oppose. Keep it to the factions that are currently relevant — don't dump your entire worldbuilding doc here.

📜 House Rules

One canonical list. Link it in every session invite. Eliminate the "wait, how does flanking work at this table?" conversation forever.

📖 Session Recaps

Newest at the top. Use the bullet-point format — not prose. Players scan, they don't read.

The Architecture Rule

Every section should answer a question a player actually asks.

• "Who was that NPC we met in the city?" → NPC Tracker
• "What's the deal with the Covenant again?" → Factions
• "Wait, what happened last session?" → Session Recaps
• "Do we use flanking rules?" → House Rules

If a section doesn't answer a question players ask, cut it or move it to your private GM wiki.

Keeping It Alive

A wiki that isn't updated after sessions is worse than no wiki — it's a source of outdated information your players will eventually distrust.

The 10-minute post-session update:

1. Add the session recap (5–8 bullets)
2. Update any NPC relationships that changed
3. Add any new NPCs who became relevant
4. Update faction statuses if anything shifted

That's it. 10 minutes. Do it while the session is still fresh.

Where to Build It

You need a wiki that lives at a stable, shareable URL your players can bookmark. Not a Discord thread. Not a Google Doc that gets stale. A permanent home.

The D&D Campaign Starter Kit on Topicfolio is structured exactly this way — world overview, NPC tracker, factions, session recaps, house rules, all in one Folio. Fork it, fill it in, share the link. No signup required for players to read it.

📂 Free template → D&D Campaign Starter Kit — everything above, pre-structured and ready to use.