Thanks Michael, seems like a good practice. I suggest also to adopt a practice that anyone who add new functionality will add a section in the user guide, even if at first it is only a title with a TBD in it. That way it will be easier to know which capabilities left to document.
Cause you know, If a code falls to the svn and no one is around to document it, does it exist? --Eli -----Original Message----- From: Bruggeman, Michael Sent: Thursday, September 10, 2009 2:06 PM To: [email protected] Subject: Apache Wink Devloper Guide Documentation Hi All, I would like to draw your attention to the "Apache Wink Wiki" site, there I have created the documentation for the Apache Wink project. The documentation, titled "Apache Wink Developer Guide" contains the latest information pertaining to the current version of Apache Wink. In order to improve and streamline the documentation process I would please ask that the following guidelines are adhered to: When adding a new topic to the TOC (or anywhere in the documentation) make sure to add underneath the heading "TDB" (to be defined), also write your name there so that I will be able to track the progress on the new topic and also review the content as well as have the name of the person who is responsible for adding the content to the Wiki. Please Note: adding your name is very important because it will enable me or anyone else to refer to the correct person, saving time. Also, please review the documentation, adding relevant points where necessary. I have finished writing the first two section of the Wiki, titled: Introduction to Apache Wink and Apache Wink Building Blocks. Please review these two chapters (sections) and send me your feedback, as I complete additional chapters (sections) I will send an e-mail notification asking for review and feedback. Your input is valuable to me, please add topics and review the wiki content. Thanks, Michael Bruggeman
