Wiki Map

EchoWiki is organized like a contributor manual, not like a blog. The left sidebar is the main route through the material.

How The Sidebar Works

The structure follows a documentation pattern used by mature engine manuals: first get oriented, then follow tutorials, then use the manual and reference sections when you need exact boundaries.

Sidebar area	Use it when
Getting Started	You are new to the repository or trying to find the right door.
Tutorials	You want a guided feature slice or a concrete worked example.
Manual	You need the big-picture architecture and runtime system explanations.
Leitmotif	You want to work on the choreography authoring app and its screenshots.
Reference	You need exact file boundaries, tools, assets, and diagnostics.
Contributing And Operations	You are preparing a change, verifying it, or deploying the wiki.

Recommended Reading Paths

First Hour

1. Start Here
2. Visual Orientation
3. Change Routes
4. Verification Guide

First Tiny Feature

1. Tiny Moddable Feature
2. Data And Modding Flow
3. Asset Loading Pipeline
4. Contribution Workflow

Runtime Work

1. Runtime Shell
2. Runtime Loop
3. Audio And Transitions
4. Rendering And UI

Tooling Or Release Work

1. CLI Tools
2. Assets And Packaging
3. Asset Pack Reference
4. Vercel Deployment

Leitmotif Work

1. Leitmotif Overview
2. Leitmotif Screenshots
3. Leitmotif Getting Started
4. Leitmotif Usage
5. Leitmotif Moddability
6. Leitmotif Architecture
7. Leitmotif Contributor Slices

Page Granularity

Pages are intentionally small enough to answer one contributor question:

• “Where does this code live?”
• “What owns this behavior?”
• “Which data file should I edit?”
• “Which command verifies the change?”
• “What must degrade gracefully if content is missing?”

When adding a page, prefer a practical contributor route over a large essay. If a page starts covering more than one workflow, split it and add the new page under the right sidebar dropdown.