Abstract:
Documents are interfaces. In situations where documents help us do tasks - whether simple or complex - they look and act like software interfaces. Academics in technical communication are in the business of helping people learn to design, build, analyze, and assess these interfaces. Yet, only occasionally do we admit this responsibility. Judging from our curricula, our research journals, and our textbooks, we still view this responsibility as somehow distinct from what we do to teach 'technical writing,' 'technical editing,' or 'document design.' It isn't.
-mail to a friend
peer-reviewed