Hello everyone, this is definitely my first post in the game design section on the forums. I don't plan on being a designer (as I'm very into programming), but I would like to write up a proper design document for the game I'm working on, that way other people on the team have an idea as to what I have in mind for the game. I'm wondering if there are any good resources concerning how to structure the design document, how detailed to be, etc. I pulled up the Grim Fandango Puzzle design document. As interesting as it was, I'm looking for more of a "complete" version. Basically, how to list off game feature, technologies used, etc. If anyone here has written a design document, and is willing to send it to me as an example, I'd very much appreciate it. If not, any advice would help, as to how to manage/properly start this document. Thanks! :-D

Tom Sloper has an outline for one on his website, Sloperama.com. You can also check out the document on the writing page of my website (linked in my sig) that uses a format provided by Patrick O'Luanaigh in his book Game Design Complete. Both of these should be a good starting point, but don't feel the necessity to follow either to a T. Different projects and differences in knowledge of the people working on a project are going to dictate different levels of detail.

Quote:

Original post by F1N1TY technologies used, etc.

That would be a TDD. It's standard to write both a GDD and a TDD. Read postmortems, search smarter, get books. You'll find the information you seek.