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.
Interesting. You may have hit on something Eric in trying to define modular documentation. I hope I'm not coming totally from some other planet here but here is MY impression of modular documentation.
I was first introduced to what was called modular documentation when I did InfoMapping in my first writing gig. That worked on the concept of writing in "chunks" of information. Now, I am also doing what they call modular documentation in XML. I write (until Monday) in Arbortext Epic Editor and use SigmaLink as the Electronic Document Management System (EDMS). All the topics and subtopics are broken up into "chunks" of information and written into Document Type Definitions (DTDs). The finished products, or chapters and topics are now in modules and containers. They are then linked together into a manual and previewed into a PDF document and sent out to the field electronically. These "chunks" or modules can be reused and linked to other manuals. Does this help or is everyone just confused on a higher level now?
