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.
> Currently, the tech doc source files of all three companies are far-
> flung in Windows Explorer directories living on servers and hard drives
> God knows where. My company has very basic SharePoint, which by itself
> is not workable for complex documents that involve dozens or hundreds
> of graphics file, each of which would have to be signed out
> individually. We are looking at SharePoint front ends that might work.
What source control tool does each company use for software development? Are there plans to standardize that? I'd look at that before thinking about buying something new, especially if the developers are using an open source tool like SVN or CVS.
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-903-6372
------
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
