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.
That is such a broad topic that dozens of books have been written on
My suggestion...if you need generic manual for client/server, submit
a booklist from Amazon.com.
If you need it specific to your situation...find one that turns you
on...(visit your local B&N, Borders, etc.,) buy it and create your
manual following the structure of the book. Don't copy the book or
sections, but the TOC should give you a head start.
> I've been asked to write a client/server manual for clients who
> will be
> configuring and maintaining the client/server environment. This
> should describe client/server components and the basic architecture
> of our
> software. I am trying to map out a doc plan/TOC. However, we don't
> have an
> existing client/server manual, and I know little about the subject.
> If you
> can shed some light on the type of information that should be
> included a
> client/server manual, I would appreciate hearing from you.
Technical Writer mailto:john -at- tdandw -dot- com
"Hammers, Screwdrivers and Scissors"
An "I Can Do It" Book
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/