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.
David Locke continued the discussion of mapping with the
observation <<So maybe, in our hypertext systems, we need to
stop thinking about jumps (link) as just a way to move from one
paragraph (node) to another, and start thinking about jumps as
relationships.>>
Makes sense to me. That's the sort of thing we try to do with
image maps and tables of contents, but those tools seem relatively
static and uninteresting. Anyone else want to pick up the thread
and explore it? Sample topics to get the ball rolling:
- what are the main failures of hyperlinks, and how could
understanding the underlying "map relationship" improve our
hyperlinks?
- what is the difference between a hyperlink that simply jumps you
to another position, vs. one that expresses a relationship?
- are image maps better at showing relationships than text links?
