Indie Game Dev

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 stack categories worth comparing here:
- production planning and milestone tracking
- playtest note and bug review systems
- store-page and launch asset workflows

Open materials worth opening side by side:
- Godot engine source: github.com/godotengine/godot
The open source engine itself, useful even if you only read around the edges.
- Godot demo projects: github.com/godotengine/godot-demo-projects
One of the best public libraries for learning from small, runnable examples.
- Godot documentation: docs.godotengine.org/en/stable/
A strong open engine reference with a good balance of basics and production detail.

Working documents and guides:
- Steamworks documentation: partner.steamgames.com/doc/home
One of the few places where platform realities and release logistics are spelled out clearly.
- itch.io creator docs: itch.io/docs/creators/faq
A good counterpart for teams releasing small games outside the big-platform default.

Milestone and playtest log:

milestone:
  goal: "prove the first 10 minutes"
  must_have:
    - core movement
    - one repeatable reward loop
    - tutorialized fail state
  playtest_notes:
    friction_points: []
    moments_of_delight: []
    cut_list_before_next_build: []