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.
It's recently become apparent to me that I've been talking
w/ a variety of people about modular documentation,
but we're not communicating because we don't have
common definitions or common understandings. So,
I'm looking for a consensus, of sorts, about what
technical writers mean by the term "modular documentation".
My questions (if you respond to me offline, I'll
summarize--I'd be interested in onlist discussions
of the topic, though):
* Do you currently write "modular documentation"? Why
or why not?
* What _is_ modular documentation? (Please provide
examples or an adequate description for what your
modules look like. Are they paragraphs? Chapters?
Tasks? How do you tell a new writer what to create?)
* Do you reuse/repurpose documentation modules? Why or
why not?
