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.
This happens to me over and over: an engineer mentions a product that
they think has great documentation. I look at their docs for a few
minutes and see that (1) the product is very simple and (2) the docs
are nevertheless only around 10-50% complete.
So, sure, that looks nice and clean compared with the comprehensive
documentation I've produced for a product that's 100 times as complex.
On Mon, Jan 4, 2016 at 3:23 PM, Tom Johnson <tomjohnson1492 -at- gmail -dot- com> wrote:
> ... bleeding edge tools is that they rarely satisfy the
> requirements placed on tech writers. People want modern-looking,
> interactive websites. Then they also explain on that they need PDF
> generation, translation, multi-edit capabilities, single source generation,
> workflows, and document statuses, etc. By the time the list of requirements
> is finalized, about the only tools that satisfy them are more traditional
> tech comm tools. ...
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com