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.
Subject:Re: Web Server & Documents--long From:Folse Kate <folsek -at- BSCC -dot- BLS -dot- COM> Date:Thu, 3 Apr 1997 12:23:00 EST
Thanks bill for your response. I am still doing a lot of the
needs analysis type of research, but for a lot of the
questions, the answer is a solid "it depends"
Our initial audience is internal customers only. They will
have the client software installed on their PCs by the
SA group. All server apps and docs will reside on a
different machine.
The audience is fairly knowledgeable about Internet technology
and is really looking forward to using the Internet for
apps and docs.
>
>1. To which platforms must the documents be delivered?
> Some of your software options may be limited by this issue. It may
>also
> determine which web browser would best suit your needs.
>
The plan is to use Internet Explorer running on a Win95 and NT4.
This is a company standard and I don't have much to say about it.
>2. How are the users going to access and use the documents?
> Will they download them and read them using locally installed
>software?
The plan is to have the documents located on the web server.
We don't want to have links to word files or acrobat files within the
application itself. We'll be using a form of net help to access help. I
would like to have
an index of all docs from which the user could download/print an
acrobat version, but depending on how I choose to create the docs,
that may or may not be feasible.
> Will they print?
Doesn't everyone ;-)
Seriously though, that is why I'd like to have an acrobat type file for
the
users too.
> Will they read them online?
Ideally, they will be used as reference materials and will be read
online.
The applications aren't too complicated and once the
users are trained, they'll use the docs for quick reference.
>3. How (and by whom) are the documents going to be maintained?
Me and only me ;-/. I am the only one here. so, what I say goes.
>
>4. How are the documents going to be managed?
This is part of the research I am doing. I want to figure out how
best to develop, organize, deliver, and distribute updates -
depending on my tool(s) of choice I know I will have different
options.
>5. What additional features (multimedia, database functions) do you need
>to incorporate into your system?
Still determining that with tptb.
>I'm sure I haven't covered everything, but I hope this helps.
No, but thank you, and everyone else who is taking the time to respond.
--kate
>
>Bill Burns
>Technical Writer
>billdb -at- ile -dot- com
>
> TECHWR-L (Technical Communication) List Information: To send a message
>to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
> to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
> Search the archives at http://www.documentation.com/ or search and
>browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
>
>
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
