KVCD: Documentation ideas?
 

Now we've got the matrix and GOP stable it's definitely time to start the documentation, as others have been *cough* gently hinting for weeks :mrgreen:.

The problem is that things have changed constantly in the past and will continue to do so. Here's my list of stuff that's most likely to change frequently:

- File prediction method
- Avisynth script
- "Which template for this kind of source" guidelines

My suggestion would be to write generic guides that detail the process itself, then have links to sticky topics in the forums for the very latest formulas, scripts etc.. That way we can write the actual docs just once, and edit the stickies when we change something (i.e. several times a week :D).

Another idea is to set up a wiki site so that anyone can contribute to the docs.

Re: Documentation ideas
 

I've been doing just that for the past couple of days :D.
Still haven't made up my mind, as I'm evaluating about 5 different systems. Just to give you an idea of some I'm looking into:

(1) http://tikiwiki.sourceforge.net/
(2) http://www.geeklog.net/
(3) http://cafelog.com/
(4) http://www.blogger.com/

Don't be surprised if one morning you wake up and KVCD.Net's home page has been revamped :mrgreen: ( KVCD.Net main site and forum was set and launched in ~12 hours 8O :D )

-kwag

ummmmm.....*cough* :wink: ......wooooohooooo!!!!!!!!! :sun: :tup: :flip: :yippie: :yippie: :yippie: :yippie: :yippie: :yippie: (imagine about 500 more of these icons!).

Can't wait guys!
-d&c