Files
Brian Madison 6dd41a1d0e Merge branch 'main' into ticket-master
Five conflicts, all from main moving under this branch:

- marketplace.json: main collapsed six plugins into one and dropped
  every v6-shims entry. Took main's structure and swapped
  create-epics-and-stories for bmad-ticket in its alphabetical slot,
  leaving the shim unlisted to match the new convention.
- CHANGELOG.md: main cut v6.11.0, so this branch's Unreleased entries
  were stale duplicates of released ones. Took main's file and opened a
  fresh Unreleased section holding only the two entries that are
  genuinely new here.
- module-help.csv: main rewrote every row. Took main's and swapped the
  one row, keeping menu code CE — repointing a trigger without renaming
  it is the precedent IR set when check-implementation-readiness folded
  away, and the PM agent already does the same.
- The two create-epics-and-stories files main touched in #2704: took the
  delete. Its only change was python3 -> uv run, and the shim that
  replaced those files never called python3.

Sidebar order moved 18 -> 17: main removed the adversarial-review page,
freeing the slot this page was skipping past.
2026-08-14 18:14:01 -05:00
..

BMAD Method Documentation Site

This directory contains the Astro + Starlight configuration for the BMAD Method documentation site.

Architecture

The documentation uses a symlink architecture to keep content in docs/ at the repo root while serving it through Astro:

bmad2/
├── docs/                          # Content lives here (repo root)
│   ├── index.md
│   ├── tutorials/
│   ├── how-to/
│   ├── explanation/
│   └── reference/
└── website/
    ├── astro.config.mjs           # Astro + Starlight config
    ├── src/
    │   ├── content/
    │   │   └── docs -> ../../docs # Symlink to content
    │   └── styles/
    │       └── custom.css         # Custom styling
    └── public/                    # Static assets

Development

# From repo root
npm run docs:dev      # Start dev server
npm run docs:build    # Build for production
npm run docs:preview  # Preview production build

Platform Notes

The website/src/content/docs symlink may not work correctly on Windows without Developer Mode enabled or administrator privileges.

To enable symlinks on Windows:

  1. Enable Developer Mode (recommended):

    • Settings → Update & Security → For developers → Developer Mode: On
    • This allows creating symlinks without admin rights
  2. Or use Git's symlink support:

    git config core.symlinks true
    

    Then re-clone the repository.

  3. Or create a junction (alternative):

    # Run as Administrator
    mklink /J website\src\content\docs ..\..\docs
    

If symlinks don't work, you can copy the docs folder instead:

# Remove the symlink
rm website/src/content/docs

# Copy the docs folder
cp -r docs website/src/content/docs

Note: If copying, remember to keep the copy in sync with changes to docs/.

Build Output

The build pipeline (npm run docs:build) produces:

  • Static HTML site in build/site/
  • LLM-friendly files: llms.txt, llms-full.txt