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.
How important is it that documentation exactly follow the interface?
Hypothetical question: On the landing page of an application, functions are laid out in non-alphabetical order. There doesn't *seem* to be a functional reason for laying it out the way it is. Maybe they were developed in this order. Let's say it looks a bit random. Something like this:
* Crotons
* Abercrombie
* Donuts
* Fish
* Ectoplasm
* Birds
* Guppies
I was thinking that if I were writing the documentation, that I might lay out the docs in alphabetical order, to be more pleasing to the eye. Something like this:
Information contained in this e-mail transmission is privileged and confidential. If you are not the intended recipient of this email, do not read, distribute or reproduce this transmission (including any attachments). If you have received this e-mail in error, please immediately notify the sender by telephone or email reply.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
