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.
Our product is a Web application server. It conforms to industry standards
and therefor our customers who write applications must follow these
standards. When writing applications that run on our server they can
currently use our books which describe not only how to use our product, but
also how to write these applications. However, there are many books that
cover in-depth how to write applications.
So my doc manager had an interesting idea... why not include third-party
books that cover the basics of application development so we, the writers,
can concentrate on the more specific discussions of our product?
An example might be if the Adobe Photoshop folks started including a "Tips
and Tricks with Photoshop" book from O'Reilley (or some other company) in
their product. My question to you is what do you think of this notion? What
are the upsides/downsides? Has anyone tried it before? Is anyone doing it
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.