A tour of my FANTASY WORLDBUILDING BIBLE✨how I worldbuild in OneNote📓

A long-running fantasy project is easier to manage when worldbuilding notes live in a structured “bible” rather than scattered documents. Using Microsoft OneNote, ShaelinWrites builds a multi-level system designed to keep a single fantasy world consistent across many separate stories—so details don’t get lost as the setting grows over years.

The core setup centers on OneNote’s navigable hierarchy: a table-of-contents “shelving” structure with folders within folders and linked pages that function like a simplified wiki. Instead of writing endless blocks in Microsoft Word, the system separates world fundamentals from story-specific material. Four main categories anchor the table of contents: General (world-wide reference), Magic System (rules and types of abilities), Realms (geographic regions arranged in a horseshoe layout), and Stories (working material for multiple projects).

In General, the bible starts with a map—created in Incarnate and upgraded to a paid version when the world began expanding beyond the original map’s edges. From there, “World features” captures broad, cross-setting concepts such as blurred boundaries between natural forces and animal traits (for example, animals that seem to grow from their biome). An “Ideas” page stores unresolved threads, including mythical creature concepts that aren’t developed yet, plus a “Name Bank” that brainstorms 20 options at a time so writers can pull consistent place and character names later. A “Story ideas” area holds early story seeds.

The Magic System section mixes overview and detail through linked pages for each ability type. The project leans toward a soft magic approach—less rigid rules, more variety—while still tracking what each power does, who uses it, and how it appears across cultures. “Touch” is treated as foundational, with notes on descriptions, applications, and cultural perception. Other abilities, like “Painted singing and dancing,” remain early-stage, including the existence of at least one character who has the power but struggles with it.

Realms are organized geographically rather than alphabetically, reflecting a horseshoe-shaped world. Each realm gets a general culture template—religion, climate, government, exports, and inspiration—then expands only where needed for the stories set there. Examples include a desert-like realm where religion is shared across two regions, and a Central Asia–Mongolia–vibe realm (“Majorcon”) where animism and clan structure shape society, with culture anchored in falconry and linked ceremonies. One realm, “Ceasefire,” is built as a closed system isolated from new resources, prompting logistics-heavy worldbuilding such as a resource chart to track renewable versus non-renewable materials and the resulting value distortions.

Finally, Stories organizes each project with working titles, plot summaries, evolving outlines (condensed into five parts for a two-POV structure), chapter scene notes, and “scenes and snippets” for quick quotes or moments. Character pages are used more because the bible demands completeness than because character profiles are inherently favored. The overall goal is not just to write one book, but to create a framework that stays usable as the world expands—preventing the setting from outgrowing its organization.