Indie Game Dev

A genuinely helpful indie-dev pack should include an engine handbook, store documentation, playable demos, and reusable assets. That mix gives a small team both the building blocks and the shipping context.

Godot's docs and demo projects are useful because they make shipping feel concrete. Steamworks documentation matters because launch quality is partly a store page and distribution problem, not just a code problem. The real debates are about when to cut polish versus features, how early public marketing should start, and whether wishlists, demos, or creator coverage deserve the most attention. The right answer depends on genre, runway, and how readable the game is in ten seconds.

The tools that keep proving useful usually support production planning and milestone tracking, playtest note and bug review systems, and store-page and launch asset workflows without making the underlying work harder to understand. When you bookmark something, write down why it earned the slot.

Three sources worth opening side by side:
- Godot documentation: docs.godotengine.org/en/stable/
A strong open engine reference with a good balance of basics and production detail.
- Steamworks documentation: partner.steamgames.com/doc/home
One of the few places where platform realities and release logistics are spelled out clearly.
- Godot engine source: github.com/godotengine/godot
The open source engine itself, useful even if you only read around the edges.
- Godot official video archive: youtube.com/@GodotEngineOfficial/videos
Engine walkthroughs and announcements that are genuinely helpful for small teams.