Signup to gmail Go to the documents section Create a new document Share with other team members Add content Generate contents Export as HTML Put it somewhere eg: Petwars design doc Benefits are: Rapid development Instant team access to changes Access anywhere you have the internet Easy Hyperlinks Easy export as html Simple image import Version history Managed through a browser

Wow, your user ratings are rock bottom...

Anyway, that actually looks like a good idea... Never used google docs much... But having an example definitely helped convey what you mean. I wonder if you can make it flashy though >.>

I always thought using a wiki would be a good way to make a design doc. Take that with some salt though as I have never actually made one.

Google Docs has had it's uses for me too. Because in 2010, it's impossible to get anything other than a simple .txt file to open without installing a big program. It's been good enough for letting me print off resumes from anywhere, but other than that, it's pretty stripped down.

The wiki sounds like a much better idea.

I really have to question that one. Rich Text Files (.rtf) can hold good quality formatting and are operable by almost anything. Generally if a text program can open more than .txt, the next format will be .rtf.

Thing is though that a linear document like that does not facilitate the interlinking of subject matter, the easy editing, or the searchability that a wiki would. With a wiki, a page on a topic can be found quickly, updated, and most of the time, there is a history of revisions to look back at.

Talking abuot wikis. they do seem like an awesome idea... butreally... I hate wiki code, I never looked at one til recently but I look at it and all I can think about is.... is this some kind of new language?

Is there some sort of gui based wiki creator? That would be definitely make wiki more inviting.

Also, the google doc posted, is html based. I think that's probably second best for most, as it allows easy access to certain parts, and a complete read through if you wish.

I was an intern at a video game company that used wikis for the DD.

Overall, the system was great. The only problem is that you couldn't use it if you weren't online.

But, it was convenient.

I would expect most companies to have the "limitation" of online only usage for everything from modifying the code base to reading or changing the documents. Keeping up with changes coming form different users at different times means that it needs on location to be accessible from to eliminate outdated versions running around. Online here should mean intranet though, not open internet. Putting your design docs out on the internet seems odd for a major project.

pothb-> There are many variations of Wiki software out there and each of most of them have many plug-ins to modify them. That considered you are also writing code for a game so if the software you can find doesn't do quite what you want, change it so it does. There are already many variations on the original CamelCase wiki linking, such as having markup. That said, those things are no more complex to learn or use than BBcode or HTML.

Yea, i guess, but it just seems a bit unnecessary. Like I said though, I never looked too far into wiki. As for online, it doesn't seem too odd to me, if it were limited to users logging in, unlike the tc's design doc.

I use google docs pretty heavily. For me the pro's are the whole "cloud computing" concept as we have three computers in my home and I'm never sure which one I'll be able to get on (darn kids and their darn homework!)

Big thing I like is that in terms of formatting, layout and organization it's a lot like MS Word and Excel, both of which I've used a lot before. One major headache is that formatting is sometimes wonky and I have to edit the HTML directly, mostly to remove weird line breaks or font commands that have gone awry.

Overall though it's very effective.