Everything you need to keep your Game Design Documents alive and in sync with your game.
Documentation#
GDD Manager turns your messy notebook of ideas into a structured, exportable document that talks directly to your game engine. This documentation covers every feature in the app, why it exists, and how to get the most out of it in your project.
Where to start#
If this is your first time here, follow this path in order:
1. What is GDD Manager
A 5-minute overview of the app — what problem it solves and how it compares to a regular Notion/Confluence doc.
2. Key concepts
Understand page type, addon, wizard, and Remote Config — vocabulary that comes up everywhere in the docs.
3. Your first project
A walkthrough for creating a GDD from scratch using typed page wizards.
4. Addon reference
One page per addon type (Skills, Currency, Production, etc.) with schema, examples, and gotchas.
What's in the app#
GDD Manager is organized into three layers:
- Pages — each one represents a concept in your game (a class, a skill, an economy). Typed (with wizard) or blank.
- Addons — specialized blocks inside a page. Skills, Currency, Attribute Modifiers, Progression Table, etc. There are 16+ types today.
- Remote Config — exports everything to JSON that your engine can consume (Unity, Godot, Unreal, web). Flexible schema, multiple formats.
The real power comes from the integration between layers: a skill references an attribute modifier, which points to an attribute definition, which becomes a field in an exported JSON — all navigable and validated.
Quick links#
- Full addon coverage → Addon reference
- How to export to your engine → Remote Config
- Modeling a full RPG → Guides (coming soon)
- Ready-to-copy snippets → Cookbook