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.
I want to help them set up a document control system. Right now there's nothing -- so persons A, B, C, D, and D's great uncle can all be twiddling with different instances of the same doc at the same time, and then the poor tech writer (that'd be me) gets to figure out how to integrate all their comments back into a single master doc.
----- Original Message -----
From: "Richard Combs" <richard -dot- combs -at- Polycom -dot- com>
To: "Matt Gras" <mattgras -at- comcast -dot- net>, techwr-l -at- lists -dot- techwr-l -dot- com
Sent: Wednesday, July 24, 2013 2:27:19 PM
Subject: RE: SharePoint question
Matt Gras wrote:
> I'm contracting with a small engineering company that has absolutely no
> document control process. I'm thinking of recommending SharePoint as a
> document repository tool, and invite your comments, pro and con.
All together now: It depends!
Are they a Windows shop? Are they already using SharePoint for their intranet? What do you want to accomplish?
Or are you just bored with recent threads and hoping to ignite a good pro- vs. anti-Microsoft argument? :-)
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-903-6372
------
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
