All of those sound good. For the release of 1.1, I just want to guarantee that the install document is flawless, and the 1.0 docs are put in the background.
I'm not sure what you mean about the 1.0 docs being "done"? Thanks, Kevin -----Original Message----- From: George McLaughlin [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 8:07 PM To: [EMAIL PROTECTED] Subject: Document Question Hi All, A few questions <snip> > Thanks to all of you willing to help us with the documentation. The > easiest way for us would be to have documents that follow the Apache > document DTD used in forrest. What you have to do is: > > 0. cvs co xml-xindice > 1. d/l forrest - http://xml.apache.org/forrest); > 2. install it and set your FORREST_HOME and PATH accordingly; > 3. edit documents under src/documentation/content/xdocs (pay attention > to book.xml); > 4. run forrest from xml-xindice ("forrest site") and check out results > under build/site; > 5. repeat 3-4 until satisfied with the results :-) > 6. from xml-xindice "cvs diff -r -u > patch.txt" > 7. upload your patch to Bugzilla, expect big hugs in return. :-) <snip> OK. I'm all set up and successfully generated the "build/site" What do you want me to do from here? 1. Check the document links to make sure they are not broken? 2. Check spelling etc..? 3. Check that documentation how-to's, installation how-to's, etc. are correct? 4. Write documentation on some aspect of xindice? I will create a new tab linking to the 1.0 docs. I don't want to open up a can of worms here, but are those docs "done"? regards, george -- George McLaughlin <[EMAIL PROTECTED]>
