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.
Subject:Re: Information Presentation Question From:The Tech Writer <techwrtr -at- CRL -dot- COM> Date:Tue, 28 May 1996 13:14:52 -0700
Well, from a sparse and general description, here is a sparse and general
reply:
I would lean toward printed documentation for this type of informative
information, if that documentation could reach all of its intended
audience (that is, that it would not end up in some sys-admin's locked
cabinet). Printed seems to always work better for informative
information, because the reader can take it wherever is most
appropriate--to a boring meeting, to the beach, etc. Plus, you can put a
lot more into the design of information (sidebars, sections, reading
order) with printed than you can with online documentation.
On Tue, 28 May 1996 David_Dubin -at- notes -dot- pw -dot- com wrote:
> If you had to pick the top two (2)
> methods of presenting a block of information quickly and completely, what would
> they be and why? The information to be presented is informational, not
> procedural, and it may be lineal or linked via topics.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
