fix: resolve defrag cross-page analysis findings

[github-actions]

Summary

Addresses the cross-page analysis findings from issue #498. Each section is addressed in a separate commit. Changes focus on concrete, low-judgment items: terminology consistency, cross-references, and heading alignment.

Changes Made

Section . (root) — commit 1874a42

• Spell out "Entity-Component-System (ECS)" on first mention in overview.mdx
• Add "Autonomous Worlds" section with link to /theory/autonomous-worlds in overview.mdx
• Cross-reference AI skills between overview.mdx ↔ installation.mdx
• Add overview link from brand.mdx Core Dojo Brand section

Section client — commit f481448

• Standardize "World Manager" → "WorldManager" in unity.md to match the technical implementation (the prefab/class name)
• Rename ## Example Game → ## Example Project in bevy.md for consistency with other SDKs
• Add dojo.c foundation cross-reference to unrealengine.md

Section framework — commit a45bfad

• Add /framework/models/entities link to systems/index.md Next Steps
• Add /framework/world/permissions cross-reference to systems/architecture.md

Section getting-started — commit a4b44b9

• Standardize "World contract" → "World" in your-first-dojo-app.mdx
• Standardize "local blockchain" → "local sequencer" in your-first-dojo-app.mdx and understanding-the-toolchain.mdx
• Add next-steps.mdx cross-reference to your-first-dojo-app.mdx
• Add understanding-the-toolchain.mdx back-link to development-workflow.mdx

Section libraries — commit 6a13614

• Replace "Dojo engine" with "Dojo framework" in origami/index.mdx
• Replace "Dojo's game development framework" with "the Dojo framework" in alexandria/index.mdx

Section scaling — no commit needed

Both cross-references (execution-sharding.md ↔ sovereign-rollups.md) already exist in source.

Section toolchain — commit 382d186

• Rename ## Mining Modes → ## Block Production Modes in katana/development.md; Katana is a sequencer, not a miner
• Update frontmatter description accordingly
• Other cited cross-references (sozo→cainome, katana→reference, sozo→configuration, katana→torii, torii→katana) already exist

Section tutorials — commit cdbf20f

• Add dojo-starter tutorial link to advanced.mdx prerequisites
• Capitalize "Katana" in react.mdx prose
• Add dojo-starter LinkCard to react.mdx Next Steps section

Deferred for Human Review

Per project conventions, the following structural findings are not applied here — they require editorial judgment about user journeys:

• Redundancy removal: Duplicate game loop patterns, account management sections, model storage examples across SDK files
• Content relocations: Moving sections between files (resource tags → permissions.md, cheat codes consolidation, foundation architecture → c/index.mdx, Data Format Reference → world-interaction.md)
• bevy.md → dojo.c cross-reference: The c/index.mdx architecture overview does not list Bevy as a dojo.c consumer (Bevy uses native Rust/tokio directly); this finding may be inaccurate
• Heading standardization for step-based content: Numbered steps vs ::::steps format — cosmetic, editorial call
• Entity terminology (entity_id vs entity ID): These appear in code contexts; leaving code style decisions to maintainers

Closes #498

Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
book	Ready	Preview	Apr 22, 2026 8:04pm