- Game Design Document: The purpose of this document is to describe completely all features and illustrate clearly the functionality of the game in development.
- Pitch: The purpose of this document is to sell your ideal to a lead, prospective client, investor, or publisher.
4 min read
Opinion: Improving Your Documentation
In this reprinted #altdevblogaday-opinion piece, PixoFactor's Adam Rademacher offers some general technical writing advice on how to improve your game documentation.
[In this reprinted #altdevblogaday-opinion piece, PixoFactor's Adam Rademacher offers some general technical writing advice on how to improve your game documentation.] Game Design is about the merging of ideas and the creative evolution of complex entertainment software from idea through delivery. Nothing in this process is more important to the designer than effective communication and memory over long periods of time. Enter the role of documentation. Preface Trying to improve your documentation is a long and arduous process. Unfortunately, I don't know of any way to build these skills without practice and critique. If you have any friends who are editors or writers themselves, they can often give you good feedback — but be careful of those who work solely in creative writing. Technical writing is not creative writing, though they share some parts of their skill sets. So, I have to give you this advice: if you want to improve your technical writing, write more. What's The Point? Technical writing differs greatly from other forms of writing in its purpose, and it's important to recognize that purpose: communication. All writing is about communication, but technical writing begins with a clear understanding of the purpose of the document you are writing. Here are some examples: