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.
Confluence is easy to learn and as people get used to inline comments
and other collaborative features it makes communication much more
efficient. I can't imagine going back to FrameMaker and having to do
reviews with PDF comments or Word change markup. I'd probably have to
hire another writer or two to handle what I can do on my own with
Confluence.
I started out with a 10-user version ($10) and enabled and disabled
logins as I needed feedback from various SMEs. It very soon became
clear that a 25-user version was worth the cost ($1200).
I have a separate 10-user instance I use to test things and to keep
the cost down for add-ons such as Scroll HTML Exporter that no one
else uses.
On Tue, Jul 14, 2015 at 12:09 PM, Laura Phillips
<laurap -at- pluribusnetworks -dot- com> wrote:
>
> We just got a new program manager who mentioned that her previous company used it with "great" success. I looked at the pricing and to support the potential number of collaborators, weâd have to pay $300 per month. Given that my FM subscription is substantially less than that, I didnât really explore it any further when I was looking at options 2 years ago.
>
> I am not confident that engineering would buy into a collaborative system when I can barely get functional specs written for features. Itâs usually an email or text in a bug that requires further investigation on my part. Iâm also hesitant about the learning curve and time required to put together a working version of Confluence. Iâm still the only pubs person, and our release cycles can be brutal when supporting customer requests. We donât use Agile as a development methodology so itâs more of an ordered chaos process.
>
> Anyway, thatâs the core issue around moving to this type of authoring process.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
