@ Jess T
We definitely don't want to see your work go to waste, hopefully we will be able to get them integrated somehow.
Quote: "o A 'See Also' section for related topics.
o A 'Related Commands' section for related commands.
o A 'Tutorials' section which would have both posted code, and linked in with tutorialcity.thegamecreators.com.
o A 'Snippets' section which would have both posted code, and linked in with Nick's new Code Base.
o I was talking with Mnemonix a while back about hooking it in with the devhat IRC. So, you would call a command such as:
!tgchelp sync on
and it would return the link to http://dbp.tgchelp.com/commands/sync%20on etc.
o Periodic emails (weekly/monthly) which would email all those signed up with new changes/additions since last time.
o A downloadable CHM (Compiled HTML file) which can be stored with all the data locally on a computer (In an effort to eventually replace the standard DBP help files)."
The 'Related Commands' and 'See Also' are done perfectly in a Wiki, whenever you mention a command just put it in [[ ]]s and it becomes a link to that page.
The tutorials I think would be best on a wiki, because people can add them and adjust them at any time.
We definitely need some way of organising them, and I suggest a page only mods can edit that groups them together and shows which ones are the best.
The code snippets I think could also work awesomely, I mean, you could have a snippet, and then you could click every single command in it, and it would take you to the page for that command! Awesometacular!
The emails, I don't know if we could do that automatically...
The last bit is obviously the hardest to intergrate with the wiki (and the best). I assume that as long as people stick religiously to the templates, it should be able to automatically compile a .chm somehow?
-------------
In other news, I pasted the Command Template onto all the CORE commands. Let's start filling them out, while we decide on the overall structure of it...
-= Out here in the fields, I fight for my meals =-
