Building a D&D campaign wiki: a practical guide

A campaign wiki is one of those ideas that is obviously good and almost never survives contact with a Tuesday evening. The reason is that the traditional version front-loads all the work: choose software, host it, set up accounts for five players, decide on a page structure, write the first fifty pages — and only then does it contain anything useful.

By the time you have done that, you have spent several evenings not running your game.

Build it as a by-product, not a project

The alternative is to stop treating the wiki as a thing you build and start treating it as a thing that accumulates.

Take notes normally, one per meaningful entity — an NPC, a location, a faction, a quest, a session. When one note mentions another, link them. That's it. After ten sessions you have a linked reference for your world, and you never sat down to build a wiki.

The linking is what does it. Without links you have a folder of documents; with links you have a structure that reflects how your campaign actually connects. In Dungeon Ledger typing [[ opens a search across every note in the campaign and makes the link in a second, which is important — anything slower than that and people stop doing it mid-sentence.

One page per thing that has a name

The only structural rule worth committing to: if it has a name and might come up again, it gets its own note.

This feels like overkill at session three and is obviously correct by session thirty. The alternative — long documents covering "the northern towns" or "the villains" — fails because you cannot link to a paragraph. Something you cannot link to cannot appear in the graph, cannot be shared selectively, and will not be found by anyone searching for it.

Useful categories, most tools will let you type these:

• People: every named NPC, including the ones you improvised
• Places: anywhere the party has been or heard about
• Factions: groups with goals, which is what makes them useful
• Quests: with their current state, not just their premise
• Sessions: the log, linked to everything it mentions

The improvised NPCs are the important ones. A tavern keeper you named on the spot becomes a recurring character precisely because the players latched onto them, and if there is no note the moment you invented them, there will not be one later.

Write for the player who joins in session twenty

A good test for any wiki page: could someone who missed the first nineteen sessions read this and understand why it matters?

That mostly means writing down consequences rather than only descriptions. "A port town in the north" is a description. "A port town in the north; the party owes its harbourmaster a favour, and the Cult has an interest here" is a page worth having.

It also means keeping the current state visible. A quest page that only records the premise is out of date the moment the party engages with it. One line at the top saying where things stand now is worth three paragraphs of history below it.

Let the players read it

A wiki nobody reads is a diary. The value multiplies when the table can use it between sessions — and the only reason DMs keep it private is that it contains spoilers.

That is a permissions problem, not a reason to keep two wikis. If visibility is set per page, the players get a real reference for the world they are exploring, while the pages explaining what is actually happening sit in the same structure, linked to the same entities, hidden until you reveal them. More on that in sharing campaign notes without spoiling anything.

Use the graph

Once notes link to each other, a graph view stops being decoration. Rendering the campaign as connected nodes — people, places, quests, sessions — surfaces two things a list never will.

First, unexpected density: three seemingly unrelated NPCs all connecting to the same location usually means you have accidentally built something interesting there.

Second, dangling threads: a quest node with no recent session connected to it is a plot the party has forgotten about, and seeing it is often the fastest prep you will do all week.

Start with what is in front of you

Do not migrate five years of notes. Start with the next session: make a note for each named thing in it, link them, and keep going. The wiki gets more useful the longer you run, and the version that exists beats the comprehensive one you never finish.