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.
Re: Source control software recommendations for doc team
Subject:Re: Source control software recommendations for doc team From:Julie Stickler <jstickler -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 4 Apr 2012 15:04:17 -0400
The Drupal web page says that it is content management software. And
from my limited experience with it, it's not what we need.
What we need is source control software. Something where we can check
in/check out/lock Flare projects to prevent team members from
overwriting each others' changes. We'll do all we can to avoid
merging concurrent edits (as I remember that as being painful), but we
need a solution that allows us to merge changes if necessary.
On Wed, Apr 4, 2012 at 2:50 PM, Chris Morton <salt -dot- morton -at- gmail -dot- com> wrote:
> My understanding is that Drupal (an open source PHP tool) has come on very
> strong. There are a number of users here in this forum.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
