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've been reading some about minimalist documentation. Has anyone put
that into practice or have success/failure stories about it? Any
opinions about how it should be done--for example, in conjunction with
online help, or only with tutorial type materials? How do you think it
would work if that were all the documentation you provided for a
software program? Should it be used in conjunction with a thorough
reference manual?
By the way, my source for info about this is John Carroll's "The
Nurnberg Funnel." Are there any other sources out there about minimalist
doc? Is Carroll's book outdated?
Just interested in what other people think/have done!
--
******************************
Hillary Jones
hillary -at- nichimen -dot- com
Confucius say: Show-off always
shown up in showdown.
******************************
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
