Re: Converting to content sensitive documentation

Subject: Re: Converting to content sensitive documentation
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 20 Sep 2016 10:25:04 -0700

As far as context-sensitive help goes, not much has changed in the
past ten years. You can generate it directly from FrameMaker 12 or 13
("2015"), or you can add WebWorks ePublisher Pro to any FM version.

Since you mention Assima Vimago, is what you're looking not
context-sensitive help but an electronic performance support system?
Those tools are mostly for guiding people to fill out online forms for
HR, insurance, requisitions, expense reports, and the like, not for
other kinds of applications.

On Tue, Sep 20, 2016 at 5:28 AM, Caruso, Margaret
<Margaret -dot- Caruso -at- nexteraenergy -dot- com> wrote:
> I need to put together a plan for converting from non-structured FrameMaker>PDF>web link documentation to context sensitive help documentation. I have some experience at this - 9 years ago I used structured FrameMaker, WebWorks, and ArborText. I know a ton has changed in the last 9 years.
> I was looking at possibly using Assima, Vimago Assist. Has anyone got any experience with this? Or can you tell me what is working for you?
Visit TechWhirl for the latest on content technology, content strategy and content development |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Converting to content sensitive documentation: From: Caruso, Margaret

Previous by Author: Re: Phrasal adjective hyphenation
Next by Author: Re: Converting to content sensitive documentation
Previous by Thread: Converting to content sensitive documentation
Next by Thread: Re: Converting to content sensitive documentation

What this post helpful? Share it with friends and colleagues:

Sponsored Ads