BlaezA series bible fails the day search stops working. You type a name and get nothing — or three near-duplicates. You invent a new tag instead of reusing the old one. Places float without a region. Lore lives in both a glossary entry and a long note you never open. That is not “worldbuilding depth.” It is entropy.
The fix is boring and powerful: naming conventions, a controlled tag list, a glossary that owns definitions, and regions that locate every place. Do those four jobs and the bible stays a tool across books — not a museum of abandoned drafts. For what a bible is for, start with what “story bible” really means.
Naming conventions: one truth, many aliases
Pick rules and write them on a one-page “Style” glossary entry:
- Canonical name — the spelling used in search and manuscript tags (e.g. Elara Voss)
- Aliases — nicknames, titles, deadnames, foreign-language forms — on the same card, never as separate people
- Titles — “Captain” lowercase in running prose vs. “Captain Voss” as a name; decide once
- Houses / ships / spells — italics or not; hyphenation; plural forms
When a spelling changes for story reasons, update the card and leave a dated note (“Book 2: legally takes mother’s name”). Do not create a second card “for the new identity” unless they are literally two entities.
Continuity errors love name drift — see the cost of inconsistent characters.
If two cards share an alias, you do not have depth. You have a merge waiting to happen.
Tags: a vocabulary, not a junk drawer
Open tagging feels free until you have rebellion, Rebels, and insurgency. Series writers need a controlled vocabulary:
- Structural tags —
book-1,book-2,spoiler-book-3 - Entity type — often implied by the record type (character, location, item)
- Faction / allegiance — one tag per faction; nest details in the faction entry
- Status —
alive,dead,missing,secret - Region — or link to a region record instead of tagging every synonym
Cap the master list. When you want a new tag, check the list first. Merge synonyms quarterly. Tags exist so filters work in book four — not so book one looks decorated.
Location hooks and tags that pressure plot: setting as character.
Glossary: definitions live in one place
The glossary is not a second lore dump. It is the dictionary of the series:
- Magic terms, slang, units of measure, calendar months
- Capitalization and plural forms
- Pronunciation notes if you care about audiobook consistency
Rule: if a term needs explaining to future-you, it gets a glossary entry. Long history of a cult belongs in lore or a faction card. When both exist, the glossary points to the lore entry — it does not rewrite it.
Keep glossary lean. A thousand entries nobody reads is the same mess as no glossary — see worldbuilding without overwhelm.
Regions: every place has a parent
Series maps rot when locations are orphaned. Give geography a hierarchy:
- World / continent (optional for contemporary)
- Region — political or cultural unit (the Marches, Sector Nine)
- Location — city, ship, building, room that scenes use
Every location record links to a region. Filters then answer: “What places did we use in the Marches in book 1?” without you remembering street names. Regions also prevent duplicate cities under different spellings — search the region first.
A monthly series-bible hygiene pass (20 minutes)
- Search recent manuscript names; merge duplicate cards
- Scan tags used this month; fold new ones into the controlled list or delete them
- Add glossary entries for any invented term that appeared more than twice
- Confirm new locations have a region parent
- Mark book-number tags on entries that changed this volume
Hygiene is cheaper than a series bible rebuild before book three.
What to refuse
- A new card for every nickname
- Tags created mid-scene “just this once”
- Copy-pasting lore into both glossary and character notes
- Locations with no region because “it’s just a café”
Cafés that recur are series assets. Orphans are mess seeds.
FAQ
One bible for the whole series or one per book?
Prefer one living bible with book tags and dated notes. Per-book bibles diverge within a year.
Spoilers for future volumes?
Use a spoiler-book-N tag or a collapsed “Future” section. Do not hide future truth in a second undocumented file.
Shared universe with co-authors?
Lock the naming and tag docs first. Argue about plot after spelling is settled.
Bible + codex in one project
In BlaezForge, characters, locations, items, glossary, factions, and regions live in the same project as the manuscript — searchable together, tagged consistently, linked to appearances. Naming stays honest when the draft and the bible cannot drift into different apps.