Worldbuilding in Markdown: A Writer's Approach

A novelist's invented world dies in scattered files: a character whose eye color drifts between chapters, a city that moves provinces, a magic rule contradicted in the climax. The cure is not another worldbuilding app. It is a folder of plain markdown files, a handful of templates, and wiki-links that let the world remember itself.

Wiki-links are not a developer's trick. Wiki linking began with WikiWikiWeb, the first wiki, which Ward Cunningham launched on March 25, 1995; it linked pages by joining capitalized words together, "a technique referred to as camel case."¹ The double-bracket form — [[Veyra]] — arrived in 2001, when UseModWiki added "free links" in double square brackets alongside the older camel-case convention.² Twenty-five years on, every serious note tool reads that same syntax, and a fantasy world is exactly the kind of dense, cross-referenced web wiki-links were invented to hold.³ Patricia C. Wrede's Fantasy Worldbuilding Questions, hosted by the Science Fiction and Fantasy Writers Association and copyright 1996, opens with a warning that doubles as the thesis of this post: the list "is meant to aid authors of fantasy fiction who are seeking to create believable imaginary settings," and "it is not necessary for an author to answer all, or even any, of the questions in order to start writing."⁴ A world is built one linked file at a time, on demand, never all at once.

Why most worldbuilding notes fail

Most worldbuilding notes fail because they are hoarded, not linked. The writer fills a document with continents and pantheons before a single scene exists, then cannot find the one fact a chapter needs. The disease is not a lack of imagination. It is the absence of a structure that lets the world be retrieved as fast as it was invented.

Two failure modes recur. The first is the world bible that grows into an unsearchable monolith — a sixty-page document where the protagonist's mother is mentioned once, in a paragraph no search query will ever surface again. The second is the opposite: notes scattered across a notes app, a spreadsheet, three text files, and the margins of the manuscript, none of them aware the others exist. Both fail the only test that matters at the desk — can I find the fact I need before I lose the sentence I was writing? J.R.R. Tolkien answered this from the deepest end of the craft. In Letter 165 of The Letters of J.R.R. Tolkien, dated 30 June 1955, he wrote: "The invention of languages is the foundation. The 'stories' were made rather to provide a world for the languages than the reverse."⁵ Even Tolkien, who built worlds for forty years, anchored the sprawl to a foundation and grew outward from it. Notes without a foundation do not grow. They pile.

The folder structure that holds a world

A world is a folder tree, not an app. Six folders carry a novel for years: characters, places, lore, timeline, systems, and manuscript. Each entity is one plain markdown file. Every cross-reference is a wiki-link — the double-bracket convention wiki software settled on, now read by every major markdown tool.² Any text editor opens any file.

world/
├── characters/
│   ├── veyra-stonecaller.md
│   ├── the-archivist.md
│   └── ...
├── places/
│   ├── threshold.md
│   ├── the-ashfall-coast.md
│   └── ...
├── lore/
│   ├── factions.md
│   ├── religions.md
│   ├── languages.md
│   └── histories.md
├── timeline/
│   ├── the-long-calendar.md
│   └── arc-01-the-bargain.md
├── systems/
│   ├── magic-the-binding.md
│   └── technology-and-trade.md
├── manuscript/
│   ├── ch-01.md
│   └── ...
└── templates/
    ├── character.md
    ├── place.md
    ├── faction.md
    ├── magic-system.md
    └── timeline-entry.md

The systems folder is the one most note tutorials omit, and it is the one a fantasy or science-fiction writer needs most: it holds magic, technology, economics, politics — the rules that, once written, must never quietly contradict themselves. The lore folder holds the soft, prose-heavy material; systems holds the hard constraints. Keep them apart. A reader forgives a forgotten minor character. A reader does not forgive a magic system that breaks its own logic to rescue the hero, and neither does the genre's most-quoted craft principle, which we come to below.

The templates: characters, places, lore, magic, timeline

Templates remove the cost of the blank page. Five fenced blocks carry almost all worldbuilding: a character sheet, a place, a faction, a magic system, and a timeline entry. Keep them in templates/, copy on demand, fill the fields. Each field is a prompt, not an essay — answer only the questions a scene asks, and leave the rest unwritten.⁴

Character — templates/character.md:

# {{name}}

**Also known as:** {{aliases}}
**Lives in:** [[{{place}}]]
**Faction:** [[{{faction}}]]
**First appears:** [[ch-03]]
**Status:** alive | dead | unknown

## One-line essence
Who they are in a sentence a reader would remember.

## Appearance (lock these — continuity)
- Eye colour, height, a single distinguishing mark
- One object they always carry

## Wants
- This book: one concrete, scene-level want
- The whole story: the deeper want they may never name

## Voice
- One sentence of how they speak. A verbal tic.

## Connections
- [[Other Character]] — relationship in five words
- [[Faction]] — loyal, exiled, indebted

## Notes
(Continuity notes. Wiki-link liberally.)

The "lock these" block is the single highest-value line in the sheet. Eye colour, scars, and the family name are exactly the facts that drift between chapter three and chapter thirty. A locked file is a continuity contract with your future self.

Place — templates/place.md:

# {{place-name}}

**Region:** [[{{region}}]]
**Ruled by:** [[{{faction}}]]
**Population / scale:** {{number-or-vibe}}

## Three aspects
- A sensory aspect — what it smells, sounds, looks like
- A social aspect — who holds power, who suffers
- The wrong thing — the tension a scene can mine

## Who is here
- [[Character]] — why they are here

## What happened here
- [[Timeline entry]] — the event that marks this place

## Scenes set here
- [[ch-07]]

A place described in three aspects can be written from memory. A place described in three pages is a place the writer skips past at the keyboard.

Faction — templates/faction.md:

# {{faction-name}}

**Type:** guild | house | church | nation | cult
**Seat of power:** [[{{place}}]]
**Led by:** [[{{character}}]]

## What they want
One sentence. The thing they will break the world to get.

## What they fear
One sentence. The lever a protagonist can pull.

## Members
- [[Character]] — rank or role

## Relationships to other factions
- [[Faction]] — allied | at war | uneasy truce

Magic system — templates/magic-system.md:

# Magic: {{system-name}}

## What it can do
- Plainly. The effects a reader will see on the page.

## What it costs (the limitation)
- Every use costs something. Name it. This is the system.

## Who can use it, and who cannot
- The rule that gates access.

## What it cannot do (hard limits)
- The three things this magic will never solve.
- These are the promises you make to the reader.

## How it is known in-world
- Folk belief vs. true mechanics — the gap is plot fuel.

## Appears in
- [[ch-04]] — first on-page use

Timeline entry — templates/timeline-entry.md:

# {{in-world-date}} — {{event-name}}

**Era:** [[{{era}}]]
**Where:** [[{{place}}]]
**Who:** [[{{character}}]], [[{{faction}}]]

## What happened
One paragraph, past tense, in-world voice.

## Consequence
- The thing this event makes true for every later chapter.

## Referenced in
- [[ch-12]] — a character recalls this

Five templates. Five files. Almost every artefact a fiction writer invents slots into one of them — and the one that anchors the whole genre, the magic system, gets a section of its own next.

The magic-system file: rules a reader can trust

The magic-system file is the most load-bearing document a fantasy writer keeps, because magic is the one part of a world that fails loudly when it contradicts itself. The file's job is to record what magic cannot do as carefully as what it can. A power with no cost is not a system. It is a deus ex machina.

Fantasy's most-cited craft principle says so directly. Brandon Sanderson, articulating his First Law of Magic in February 2007, wrote: "An author's ability to solve conflict with magic is DIRECTLY PROPORTIONAL to how well the reader understands said magic."⁶ His Second Law sharpens it into four words — "Limitations > Powers" — and explains them with a line worth pinning above the desk: "Superman is not his powers. Superman is his weaknesses."⁷ The ## What it costs and ## What it cannot do sections of the template exist to capture exactly this. A magic file that lists only spells is a file that will let the writer cheat in the third act, and a reader can feel a cheat from a chapter away. Write the limitation first. The powers are easy.

Sanderson's Third Law guards against the opposite temptation — sprawl. "Expand what you already have before you add something new," he wrote.⁸ When the plot needs a power, the disciplined move is to deepen an existing rule, not bolt on a fresh one. The magic file's ## How it is known in-world section is where that depth lives: the gap between what characters believe about the magic and how it actually works is, by itself, an engine of plot. A markdown file makes the gap explicit and keeps it consistent across four hundred pages.

How wiki-links let a world remember itself

Wiki-links are how an invented world remembers itself. A wiki-link is the double-bracket phrase — [[Veyra]] — that turns any name into a backlinked node. Write Veyra's name in nine chapter files and her character page collects nine backlinks automatically. The question "where did I establish that?" stops being a search and becomes a glance.

The mechanism is the one wiki software has used since WikiWikiWeb launched in 1995, and the double-bracket form UseModWiki added in 2001 survived into every modern markdown tool — Obsidian, Logseq, and MNMNOTE all parse [[wiki-link]] identically.^{2 3} For a novelist, the payoff is continuity at scale. When a character mentions a war in chapter twenty, the writer opens the-ashfall-coast.md, reads the backlinks panel, and sees every chapter, faction file, and timeline entry that already touched that place — and writes the new line so it cannot contradict the old ones. The links assemble themselves while the writer is doing other work. Communities have refined this into formal systems: the Dataview plugin for one popular markdown tool has crossed millions of downloads and is the standard way readers of these files query "every character in this city" or "every scene where Veyra appears."⁹ None of it requires leaving plain text. The query layer is read-only over the files.

The link is the data. The renderer is replaceable. That distinction is the whole reason to build a world in markdown rather than inside a proprietary worldbuilding database — a point we return to at the close.

The pantser-vs-plotter question, settled by the file

Whether a writer outlines everything or discovers the story while writing, the markdown vault serves both, because the file is filled on demand. The plotter front-loads the templates before drafting. The pantser creates a character file the moment a name appears and fills the fields after the scene is written. Same folders. Same wiki-links. Different order.

George R.R. Martin named this divide in its most-quoted form: "the two types of writers, the architects and the gardeners." The architect blueprints the house before driving a nail; the gardener plants and tends, and finds out what the thing is as it grows. Martin counts himself "much more of a gardener," because, as he wrote in 2022, "My stories grow and evolve and change as I write them."¹⁰ A markdown vault is the rare system that does not force the choice. An architect can pre-build the systems/ and lore/ folders like blueprints. A gardener can let characters/ grow file by file, linking each new sprout back into the soil of what already exists. The five templates are scaffolding for the architect and a safety net for the gardener — the gardener fills them after the scene, turning improvisation into continuity before the next chapter can contradict it.

This matters now more than usual. NaNoWriMo, the "25-year-old online writing community-turned-nonprofit," announced at the end of March 2025 that it was shutting down, citing longstanding financial issues; the organization said the preceding year's AI and content-moderation controversies did not directly cause its demise.¹¹ Its closure scattered a generation of drafting writers — architects and gardeners alike — looking for durable systems they own outright. A folder of markdown files is exactly that: a structure that survives the tool, the company, and the year.

Pitfalls common to worldbuilders

Some habits feel like worldbuilding but produce nothing a chapter can use. Encyclopedic front-loading, contradiction without a single source of truth, decorative conlangs, and prose written into reference files all cost hours and return continuity errors. Cut them. Each one is a way of mistaking the feeling of building a world for the act of writing one.

The anti-patterns, ranked by how much time each wastes:

1. Encyclopedic front-loading. Three folders of pantheons, dynasties, and trade routes written before chapter one will be rewritten the moment a scene actually needs them. N.K. Jemisin's worldbuilding workshop names the corrective in its title: Growing Your Iceberg: Crafting a Secondary World That Feels Ancient in 60 Minutes or less.¹² Show only the tip. The bulk stays underwater — present, but unwritten until a scene calls for it. Build outward from the scene, not inward from the index.
2. Contradiction without a single source of truth. If a fact lives in three files, it will eventually disagree with itself. Each entity gets exactly one file. Everything else links to it. The character's eye colour is settled in veyra-stonecaller.md and nowhere else.
3. The conlang you will never finish. Tolkien built languages first because he was a philologist; almost no one else should.⁵ A naming convention — three syllables, hard consonants, no apostrophes — does more work in a chapter than a grammar no reader will parse. Keep it in lore/languages.md as a one-paragraph style note.
4. Prose drafted into reference files. A character sheet is not the place to write the character's tragic backstory in full scene. Write the scene in manuscript/; keep the sheet to facts and links.
5. A magic rule with no cost. Covered above, and worth repeating: a power without a limitation is a plot hole the writer has not noticed yet. The template's ## What it cannot do section is the cheapest insurance in the vault.
6. The timeline you never reconcile. An in-world calendar that the chapters quietly ignore is worse than no calendar. Reconcile the timeline/ folder against the manuscript once per arc, the way the place files get reconciled — or delete the calendar and track events by chapter only.

Each habit produces the sensation of progress without producing anything the next chapter needs. Patricia Wrede's framing again: answer the questions a scene actually asks, and leave the rest unwritten until it does.⁴

Where MNMNOTE fits

The system is editor-agnostic. The files are plain markdown; the wiki-links are double-bracket syntax; the templates are fenced blocks. Obsidian, Logseq, a code editor, and MNMNOTE all open the same folder and parse [[wiki-link]] identically.³ The point is the system, not the app. MNMNOTE is one reader of the vault; a Dungeon Master reaches the same conclusion.

The DM's version of this workflow runs in our guide to organizing a D&D campaign in markdown — same folders, same wiki-links, aimed at running a game rather than writing a novel. Open a tab, paste the templates above, and the same world travels to any device with a browser. The files remain plain markdown either way — the world is yours, in a format that outlasts the editor.

Frequently asked questions

Six questions surface in nearly every fiction writer's first month with a markdown worldbuilding system — about app choice, World Anvil and Scrivener equivalence, conlangs, plotter-versus-pantser fit, magic-system tracking, and where the manuscript itself belongs. Each answer below carries the working consensus from the craft sources cited above.

Do I need a special worldbuilding app, or will any markdown editor work?

Any editor that opens markdown files and renders [[wiki-links]] works — Obsidian, Logseq, a code editor with a markdown plugin, or MNMNOTE in a browser. The folder structure and the five templates are the system; the editor is interchangeable. Keep the files plain, because they outlast whichever app you start in.

How is this different from World Anvil or Scrivener?

World Anvil is a structured worldbuilding database where every character and place is a typed, validated record; its paid Guild tiers started at $4.50 a month billed annually and ran to $25.00 for the professional tier as of June 2026.¹³ Scrivener is a manuscript-and-research workspace in a proprietary project file. Both are good tools. The markdown vault trades their typed fields for portability and outright ownership.

Should I build a constructed language for my world?

Almost never to the depth Tolkien did. He invented languages first because he was a philologist, and wrote that "the invention of languages is the foundation" of his work — but he was the exception, not the model.⁵ For nearly every writer, a one-paragraph naming convention beats a grammar no reader will parse.

Does this work if I'm a pantser who doesn't outline?

Yes — the vault is built for it. A discovery writer creates each file the moment a name first appears, then fills the template fields after the scene is drafted, turning improvisation into continuity. George R.R. Martin's "gardener" works this way: plant the seed, see what grows, record what grew so the next chapter cannot contradict it.¹⁰

How do I keep my magic system from contradicting itself?

Write the limitations before the powers, and keep them in one file. Brandon Sanderson's Second Law — "Limitations > Powers" — is the working rule: a reader trusts magic they understand and distrusts magic that bends its rules to save the hero.⁷ The template's "What it cannot do" section lists promises. Reconcile every on-page use against it.

Where do I keep the manuscript — same vault or separate?

Same vault, in a dedicated manuscript folder, so chapters and worldbuilding files can wiki-link to each other. When a character mentions a war in chapter twelve, the chapter links to the timeline entry, and the entry's backlinks show every chapter that touched that event. Keeping prose and reference together makes continuity-checking a glance, not a search.

The world is the files

A world deserves a notebook that respects plain text and links its own continents. Build it in markdown — six folders, five templates, and wiki-links — and the world becomes searchable, portable, and yours in a format that survives every app that ever opens it. The discipline is the system. The files are the world.

MNMNOTE (mnmnote.com) opens this exact vault in your browser, with no account and no install.

References

All URLs verified live as of 2026-09-23.