>Dori Green said: >>Lisa wrote: >> >>* What do you think of the idea? >>* How/for what would you use it? >>* Would you use it regularly? >>* Would you contribute to it as well as read it? > >1. I think the idea is interesting, and could be a good way to learn about >such things. [] >2. As I'm understanding from some research and the discussions, a wiki >would be a place to collect technical writing "best practices" -- those >tasty bits that take our efforts from "compliance with requirements" to >"wow". Of course, we could also include compliance topics.
This, and much, much more. >3. Define "regularly". Check it once in a while? Certainly. See www.Metamucil.com >4. With collaborators/editors, gladly. Actually, a possible problem could arise if all members had rights to modify the information on the wiki. We would definitely need rules for this. For example, if I posted a link to what I believe is the definitive answer on capitalization, and Carla finds a more recent link, does she simply erase mine and paste her link? Should there be a verification process? - Jim _______________________________________________ Are you a Help Authoring Trainer or Consultant? Let clients find you at www.HAT.Matrix.com, the searchable HAT database based on Char James-Tanny's HAT Comparison Matrix. Contact [EMAIL PROTECTED] for details. Interested in Interactive 3D Documentation? Get the scoop at http://www.doc-u-motion.com -- your 3D documentation community. _______________________________________________ Technical Communication Professionals Post a message to the list: email [EMAIL PROTECTED] Subscribe, unsubscribe, archives, account options, list info: http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com Subscribe (email): send a blank message to [EMAIL PROTECTED] Unsubscribe (email): send a blank message to [EMAIL PROTECTED] Need help? Contact [EMAIL PROTECTED] Get the TCP whole experience! http://www.techcommpros.com
