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.
Document the product as it stands before the customizations are made.
Then you have your source. Have your solutions folks modify the source
to fit the customer installation, and charge for it accordingly. If the
customers make their own modifications to the product, it's up to them
to instruct their users on how to use it, else enter a support agreement
and charge accordingly for the content modifications.
All in all, if this is only for UI changes on a web-based application,
the UI should allow for editable tool tips so they can throw in a quick
bit of help text for the renamed button and be done with it at that
level.
BILL SWALLOW
Information Design & Development Professional
tel/fax: 518.371.1867
wswallow -at- nycap -dot- rr -dot- com
::: -----Original Message-----
::: These question is mainly for people who document enterprise
::: web-based applications?
:::
::: Do you externalize parts of your product for customer
::: modification, i.e. field names, object names, etc.?
:::
::: so potentially you could have 100 different customers
::: calling a widget, a 100 different names.
:::
::: If you do, how do you handle keeping the documentation
::: straight with the customer modifications?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
---
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.
