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.
We have a couple of good threads going now, but I'd like to add one
more. I'm reading R.John Brockmann's book, Writing Better Computer
User Documentation, and specifically the section on minimalist
document design. The design, as he defines it, "slashed 75% of the
pages by cutting previews, reviews, index, practice exercises. . ."
etc. and "left procedural details deliberately incomplete to encourage
learner exploration. . ." This type of design seems to go against
all the principles I was taught. Do many of you technical writers
use this design? Can anyone cite some examples that I might look
at?
