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.
What HAT are you using? (RoboHelp, Doc-to-Help?) I'm in a similar
situation-we write our own in-house financial/account software-and my
help system is in its infancy. The content will change greatly as we
develop our new system. However, I am the only person in control of the
help system. I keep the proto-beta (I guess that would be gamma or even
delta) help system on our server, revise the source files (HTML or MS
Word) as necessary, and recompile the help files.
I don't know if that helps. The only problem I have with end-users
customizing their own content is the possibility for headaches down the
road-"Um, the format is all screwed up," etc. I'd feel more comfortable
getting the customer's changes, recompiling the help system, and
shipping it to them.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-