> I put your question to a colleague (an interaction
> designer who's a big Cooper fan) and this is his
> response:
thanks, Steve
> "I think it DRAMATICALLY effects HOW you document
> product functionality and less what documentation you
> produce (especially the final form of the
> documentation)."
>
> Ultimately, then, you can create whatever
> documentation you feel is appropriate and deliver it
> as you would documentation produced in any other
> software development environment.
That's my question...How the document is written. I've already
established that the form is printed documentation.
> > I'd like to find out how anyone has applied these
> > concepts to printed documentation.
=====
John Posada
Senior Technical Writer
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
ROBOHELP X5 - SEE THE ALL NEW ROBOHELP X5 IN ACTION!
RoboHelp X5 is a giant leap forward in Help authoring technology, featuring all new Word 2003 support, Content Management, Multi-Author support, PDF and XML support and much more! View an online demo: http://www.macromedia.com/go/techwrldemo
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
