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'm never finished in the sense that there's always work in progress.
The final doc for each release is a snapshot of the topics in
Confluence's database with draft content excluded. If I have to ship
before I'm really done documenting the release, I release an update as
soon as possible, typically two or three weeks later.
Technical details aside, this is the same method I used for years with
FrameMaker.
On Mon, Apr 11, 2016 at 6:03 PM, Keith Hood <bus -dot- write -at- gmail -dot- com> wrote:
> It depends on how you define "finished". To ship with the product, the
> documentation has to be clear, concise, well organized, easy to use, and
> complete *as far as adequately covering the most important and most likely
> uses of the product*.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
