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.
> On Fred's note, screen captures are a great boon to the visual learner, as
> well as the non-native English speaker. We are supposed to be addressing
> different kinds of learning, right?
Good point. But screen dumps aren't the only ways we can help non-native
speakers etc. learn from documents. If we analyze an audience to determine
their level of ability, reading goals, and reading tasks, we can organize
and present information in ways that help them process it most effectively.
This is especially important when the audience has a wide distribution of
ability levels and goals. By developing an understanding how and why people
are reading the text, writers can apply design elements, graphics,
formatting, etc. that will aid more than one type of learner/user/reader.
I've found also found this to be true in teaching a Technical Writing
class. I have several non-native speakers and students in a wide variety of
engineering specialties. To help them, I use real life examples from their
disciplines (when I can find them), a little theory, and refer to specific
pages/sections in the book. I get a little redundant sometimes, but it's
worth it if I can reach a student through *their* learning channels.