Waxing Workshop: Like Onions, Stories Have Layers

Waxing Workshop: When the light returns, we build. First-quarter craft workshop posts on story structure, world building, lore consistency, revision sorcery, and the writer’s path.

Waxing Workshop: Like Onions, Stories Have Layers
Photo by Josie Weiss / Unsplash

As the waxing moon swells in the sky, it calls us to build with intention. For writers crafting immersive worlds, a common shadow looms: How do you construct a setting that pulses with life, yet doesn't bury your story under endless details?

Worlds like Tolkien's Middle-earth or Le Guin's Earthsea thrive because they serve the narrative, not overshadow it, but many of us spiral into rabbit holes of maps, languages, and histories that stall our progress.

At the heart of effective worldbuilding lies balance, and balance is achieved when elements are put into place to support your story, not weigh it down.

Let's break this down into four key principles: Relevance, Layers, Consistency, and Sensory Immersion. Drawing from literary examples and debunking myths, you can reference them and use them as tools to audit your own work.

The Four Principles

  • Principle of Relevance: Build Only What Serves the Story
    You don't need a "complete" world upfront— that's a perfectionist trap that kills momentum. Instead, focus on details that reveal character, advance plot, or heighten tension. In Dune, Frank Herbert's Arrakis isn't exhaustively mapped; its spice-driven ecology directly ties to Paul's arc.
  • Principle of Layers: Start Small, Scale as Needed
    Worlds feel alive through progressive revelation, like peeling an onion. Begin with a "nucleus"—one defining fact (e.g., "magic drains life force")—and layer outward. In Celtic myths, the Otherworld overlaps reality in thin places, revealed gradually. No need for front-loaded info dumps; use "iceberg theory" where 90% stays submerged.
  • Principle of Consistency: Weave a Web, Not a Tangle
    Inconsistent lore breaks immersion faster than bad grammar. Build a "lore web": Connect elements logically (e.g., if dragons hoard gold, how does that affect economies?). Andrzej Sapkowski's monster ecology ties to human flaws, creating ripple effects. Consistency isn't rigidity—allow evolution, but track changes.
  • Principle of Sensory Immersion: Ground in the Five Senses
    Worlds come alive through touch, taste, sound, smell, and sight, not just visuals. Over-relying on sight leads to flat descriptions; multisensory details make settings memorable. In N.K. Jemisin's Broken Earth, the earth's volatility is felt in tremors and ash-scented air.

These principles form a flexible forge: Adapt them to fantasy, sci-fi, or historical fiction. You can reference this as a checklist in your writing setup for quick audits (or even build yourself a template onion diagram), ensuring your world enhances rather than hinders your tale.

Audit Your World

Now, let's hammer these principles into practice with four practice activities. Do them in sequence or pick one, just aim for 15-30 minutes each, using your Logseq for notes.

  1. Relevance Audit: Prune Your Overgrowth
    Step-by-step: List 10 world details from your project. For each, rate 1-5 on story relevance (does it drive plot/character?). Cut or repurpose anything below 3. Example: If "elven politics" doesn't affect your hero's quest, save it for a side story. For pantsers, apply retroactively to a draft scene. Stuck on cuts? Ask, "Does the story collapse if I remove this?"
  2. Layered Nucleus Build: Grow from the Core
    Start with one nucleus fact (e.g., "Water is currency in a desert world"). Branch to 3-5 layers: How does it affect daily life? Conflicts? Senses? Draw a quick mind map in Logseq or your own visual diagram of your story onion. For series, layer across books. Feels too vague? Ground it in a character's POV.
  3. Consistency Web: Connect and Test
    Pick three interconnected elements (e.g., magic system, geography, culture). Note cause-effect links (if magic requires blood, how does that shape rituals?). Add "stress tests" by changing one variable and check for breaks. Logseq tip: Use linked references for easy updates.For historical fiction, web real events with fictional twists. Inconsistencies emerging? Create a "change log" block to track evolutions without retconning.
  4. Sensory Immersion Drill: Vivify a Scene
    Choose a location and write a paragraph describing it through all five senses, tying back to principles (e.g., relevant to conflict). Then, integrate into an existing scene. A forest isn't just "green"—it's rustling leaves (sound), damp earth (smell), thorny underbrush (touch). For minimalists, limit to 2 senses per scene. Over-describing? Time yourself to 5 minutes—focus on active, story-serving details.

These exercises yield immediate wins: A tighter world ready for your next writing session. Share results in replies for community tweaks!


Integrate these tools into your writer's toolbox and tell me your thoughts, but start simple: Apply these principles during planning or revisions—perhaps via a Logseq template with dedicated blocks for audits and webs.

For advanced variations, scale up: Turn the lore web into a series arc framework, where nucleus facts evolve across books (e.g., a world's magic weakening over time mirrors character growth). Or, for collaborative projects, share webs with beta readers to crowdsource consistency checks.

Long-term strategy: Cycle with the moon—use waxing phases for building exercises, full for reading aloud, waning for pruning. This rhythms your practice, preventing burnout amid life's chaos. Track your progress in your Logseq journal to see how your worlds strengthen over months.

What's your takeaway?

Reply with exercise results, a built world snippet, or questions—your input shapes future workshops, like deeper dives into sensory tools or Logseq integrations. Together, we build stronger castles.

~ Junior
P.S. If something is urgently broken in your template, reply with “SOS” and we’ll get straight on it.

Subscribe to J.R. Warden

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe