TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> mlist -at- safenet-inc -dot- com wrote:
> > Has anybody mentioned..... (drumroll, please)... Wicki-wickis?
> Oh, man, that's the post I didn't make.
> I fired-up my first instance of Instiki today, and let me tell you
> it's sweet. It runs under Ruby-on-Rails, created by the fine folks
> at 37signals.com, who've used it to also bring you BaseCamp
> (basecamphq.com), Backpack (backpackit.com), and Ta-Da Lists
> (tadalist.com), as well as Instiki (instiki.org). These are some of
> the finest, most useful web applications around -- and the devs just
> _happen_ to live at my webhost (TextDrive.com).
> Of particular interest to techcomms are Instiki's easy configuration
> and customization, valid and well-formed (thus accessible and
> portable) markup, and native export of zipped HTML (with working
> links), zipped TeX, and PDF.
> If you're examining wiki tools, don't leave Instiki out.
Thanks for that. I'll have a separate question in another post...
When I raised the earlier question, I had in mind more of a
general discussion of the Wiki concept and its usefulness for
corporate customer documentation.
I already know that it works impressively for encyclopedia, and for
internal corporate info-sharing. However, in the first instance,
it is wide open and everybody knows it, and takes the found info
with a grain of salt. In the second instance, there is a certain
amount of control over mischievous/malicious editing, so people
are fairly careful about what they write.
It seems to me that most complex, widely used software and
combination (hardware-and-software) products have benefitted
from user groups to supplement the documentation provided by
the producing company.
Does anybody see a way to easily and usefully combine a Wiki
with product documentation, or to replace some/all product
docs with Wiki?
Is it being done by any company, yet, in an integrated fashion?
By that, I mean more integrated than the company happens to
host a Wiki that happens to refer to their product(s).
The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
New from Quadralay Corporation: WebWorks ePublisher Pro!
Completely XML-based online publishing. Easily create 14 online formats, including 6 Help systems, in a streamlined project-based workflow. Word version ships in June, FrameMaker version ships in July. Sign up for a live, online demo! http://www.webworks.com/techwr-l
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.