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.
Ryan Young said, "We're also working on defining what each guide should be.
The other tech
writer here has pushed for combining installation, configuration, and
common operator tasks into an "Operations" guide. I feel like that's a bad
idea as it makes users effectively search through two irrelevant guides. It
sounds like the consensus here would be to separate out those three topics?"
______________________________________
I think it depends on whether the installation and configuration, and other
operational activities are connected and who will be doing them. When I
worked on documentation for bank automation software, there were user
guides, administrator guides, and installation/ configuration guides.
The installation and configuration of a dedicated server and software that
ran the web application for a financial institution was installed by IT
professionals, and was usually done once, except for subsequent software
upgrades, also done by IT staff. The administration guide contained account
configuration instructions for the bank administrative staff who set up the
individual customer accounts. The user guides for the customers contained
account setup information for each customer to set up accounts for that
customer's employees authorized to use the banking application.
So my advice is to analyze each type of configuration and assign it to a
specific user role. After that analysis, consider the various roles, and how
they may overlap. Add then decide which roles require distinct configuration
instructions, and how you will deliver them.
Margaret Cekis, Johns Creek GA
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com