One problem I’ve repeatedly run into while working on my own game is that documentation and implementation slowly become two different versions of the same game.
The GDD says one thing, the current build does another, and after enough changes it becomes difficult to know what’s still relevant, what’s implemented, what’s pending, and what was simply abandoned.
That’s why I built Strudo.
Instead of treating game documentation as one large free-form document, Strudo structures it into documentation types, blocks and relationships between systems. The goal is to make the documentation reflect how the game itself is structured, while keeping the information useful to the whole team.
Strudo doesn’t use AI to generate or organize the documentation. The structure is native to the application.
There’s a permanent free individual plan, and I’m currently opening Early Access to developers who want to try it on a real project and help shape the product.
- Demo: Mario Bross. (ES) — Mario Bross. | Strudo
- Early Access: Acceso to Strudo