RE: documenting desktop to web application

[Goober Writer <gooberwriter -at- yahoo -dot- com>]

Right. There is a difference between a User Guide
(which is what they asked for) and a document
outlining the core functionality in a way that would
show its transition.

Document it as-is. Make the users happy. If Dev wants
a migration reference, write that too. But don't try
to marry the two. They are two completely different
documents for different uses by different people.

--- John Posada <JPosada -at- book -dot- com> wrote:
> Goob...I'm with you. I don't get the problem.
> 
> Today: This is the product now. Document it.
> 6 month from now: This is the product. Document it.
> 1 year from now: This is the product. Document it.
> 18 months from now: This is the product. Document
> it.

=====
Goober Writer
(because life is too short to be inept)

"As soon as you hear the phrase "studies show",
immediately put a hand on your wallet and cover your groin."
      -- Geoff Hart

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.