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 one thing for developers to invent names for things that may help them
remember where they are, and for that context, calling a tab a "subsubsubtab,"
or a "level three tab" might have a purpose. Using the same terms in end user
documents is another matter altogether. When you want to tell users to click on
a tab, tell them to click on a tab.
----- Original Message -----
From: "Mike Starr" <mike -at- writestarr -dot- com>
> Those of us without fear tend to whup the developers upside the head when we
> encounter such poor design in a product we're trying to document. However,
> despite our tender ministrations, sometimes the developers ignore our sage
> advice and that sort of foolishness escapes into the wild and we're stuck
> describing a really crappy user interface. In those cases, to further distance
> ourselves from a poorly-designed product, we remove the instances of our own
> name that we usually put into screen captures.