Skip to content

D&D GM Planning System - Project Context

Purpose Statement

This MkDocs instance is a private GM workspace for AI-assisted campaign development. It serves as a document-driven development environment where game content is iteratively created, refined, and prepared for deployment to Foundry VTT.

This is NOT: - A player-facing documentation site - The final presentation layer for game content - A replacement for Foundry's journal system

This IS: - A GM's AI collaboration sandbox - A markdown-based planning and iteration system - A staging environment for campaign content - A version-controlled workspace for tracking campaign development

System Architecture

The Three-Stack Ecosystem

┌─────────────────────────────────────────────────────┐
│                   GM WORKSPACE                       │
├─────────────────────────────────────────────────────┤
│                                                      │
│  docs-dnd (MkDocs)          Port: 8925             │
│  ├── AI Planning Sandbox                           │
│  ├── Campaign Development                          │
│  └── Content Iteration                             │
│                                                      │
├─────────────────────────────────────────────────────┤
│                 COORDINATION LAYER                   │
├─────────────────────────────────────────────────────┤
│                                                      │
│  dnd-r (Rallly)             Port: 8927             │
│  └── Session Scheduling                             │
│                                                      │
├─────────────────────────────────────────────────────┤
│                   GAME TABLE                         │
├─────────────────────────────────────────────────────┤
│                                                      │
│  Foundry VTT                Port: 8926             │
│  ├── Production Environment                         │
│  ├── Player Interface                              │
│  └── Journal System (receives refined content)      │
│                                                      │
└─────────────────────────────────────────────────────┘

Content Development Workflow

1. Planning Phase (MkDocs)

  • Brainstorm with AI on campaign ideas
  • Draft NPCs, locations, plot hooks
  • Create encounter designs
  • Write handouts and lore documents
  • Iterate multiple versions quickly

2. Refinement Phase (MkDocs)

  • Review and edit AI suggestions
  • Organize content into logical structures
  • Add GM-only notes and reminders
  • Version control all changes

3. Deployment Phase (Foundry)

  • Copy finalized markdown content
  • Import into Foundry journal entries
  • Configure permissions and visibility
  • Add visual assets and maps

Directory Structure

/home/dockyard/docs/dnd/
├── PROJECT_CONTEXT.md          # This file - system overview
├── AI_CONTEXT.md               # How to refresh AI context
├── index.md                    # Documentation hub
├── foundry-proposal.md         # Initial pitch document
│
├── campaigns/                  # Campaign-specific content
│   └── [campaign-name]/
│       ├── sessions/          # Session plans and notes
│       ├── npcs/              # NPC descriptions and stats
│       ├── locations/         # Location descriptions
│       ├── handouts/          # Player-facing documents
│       └── gm-notes/          # Private GM planning
│
├── templates/                  # Reusable templates
│   ├── npc-template.md
│   ├── location-template.md
│   ├── session-template.md
│   └── handout-template.md
│
└── archive/                    # Completed/old content

Key Principles

Document-Driven Development

  • Treat campaign content like code
  • Use version control for tracking changes
  • Iterate quickly in plain text
  • Deploy when ready

AI Collaboration

  • MkDocs provides clean markdown environment
  • AI can easily read/write markdown files
  • No UI complexity to navigate
  • Full content visible in filesystem

Separation of Concerns

  • MkDocs: Planning and iteration
  • Foundry: Presentation and gameplay
  • Rallly: Scheduling and coordination

Technology Choices

Why MkDocs?

  • Pure markdown files (AI-friendly)
  • Git-compatible for version control
  • Live preview for immediate feedback
  • Minimal overhead for quick iteration
  • Material theme for pleasant editing experience

Why This Architecture?

  • Portability: Markdown transfers perfectly to Foundry journals
  • Simplicity: No complex tools between GM and ideas
  • Privacy: Players never see the iteration process
  • Efficiency: AI can work directly with filesystem
  • Flexibility: Easy to reorganize and refactor

Content Types to Develop

Session Materials

  • Session outlines and scene descriptions
  • Encounter designs and battle maps references
  • NPC dialogue trees and motivations
  • Clue progressions and revelation pacing

World Building

  • Location descriptions and histories
  • Faction relationships and goals
  • Cultural details and customs
  • Timeline of events

Player Resources

  • Handouts and in-world documents
  • Maps and navigation aids
  • Item descriptions and lore
  • Quest objectives and rumors

GM Tools

  • Random tables and generators
  • Quick reference sheets
  • Campaign timelines and calendars
  • NPC relationship webs

Integration Points

From MkDocs to Foundry

  1. Content is drafted in markdown
  2. GM reviews and finalizes
  3. Copy markdown to Foundry journal
  4. Foundry renders for players

From Foundry to MkDocs

  1. Session outcomes documented
  2. Player decisions recorded
  3. World state updated
  4. New plot threads added

Maintenance Notes

  • All content is in /home/dockyard/docs/dnd/
  • Docker container: dnd-docs on port 8925
  • Access at: http://[host]:8925
  • Auto-refreshes on file changes
  • Read-only mount ensures safety

Future Enhancements

Planned Features

  • Automated Foundry journal sync
  • Template generation scripts
  • AI prompt library for common tasks
  • Campaign continuity tracker

Potential Integrations

  • Git hooks for auto-deployment
  • Foundry API for direct updates
  • Backup automation
  • Content validation tools

Remember: This is your private workshop. Players experience the magic in Foundry, but the magic is made here.