Re: Using wickies

Wiki and wiki are the accepted spelling. I only mention this so you can maintain your cred with your SMEs. I've been using a Wiki based on TWiki software for the past two years. I see no problem in using one to collaborate, as long as you ensure it has these features: - Notification:

Using wickies

"Wiki" and "wiki" are the accepted spelling. I only mention this so you can maintain your cred with your SMEs. I've been using a Wiki based on TWiki software for the past two years. I see no problem in using one to collaborate, as long as you ensure it has these features: - Notification:

Using wickies

Our Honeywell doc group is currently using Frame 7.1, but we're considering using a wicki as a doc review center.  Have any of you used a wicki as a joint-authorship medium--that is, have reviewers and/or customers actually collaborate on the same wicki file that eventually becomes the finished

Re: Using wickies

I've only used a wiki review process a couple times, but it was way clunky, at least from the writer's point of view. As far as editing it up to a documentation standard for customer distribution goes, you certainly could do it with enough time and cycles... probably more cycles than in a doc

Using wickies

I've only used a wiki review process a couple times, but it was way clunky, at least from the writer's point of view. As far as editing it up to a documentation standard for customer distribution goes, you certainly could do it with enough time and cycles... probably more cycles than in a doc

Using wickies

Our Honeywell doc group is currently using Frame 7.1, but we're considering using a wicki as a doc review "center."? Have any of you used a wicki as a joint-authorship medium--that is, have reviewers and/or customers actually collaborate on the same wicki file that eventually becomes the