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.
Subject:RE: What would replace WebHelp? From:"Wroblewski, Victoria" <vwroblewski -at- NECsphere -dot- com> To:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>, John G <john -at- garisons -dot- com> Date:Thu, 29 Sep 2011 10:33:13 -0500
-----Original Message-----
From: McLauchlan, Kevin
Sent: Thursday, September 29, 2011 10:03 AM
To: John G
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: What would replace WebHelp?
>>>
Anyway, the important part of the criterion that you mention was not that it used frames, but that it gave the user a decent suite of navigation tools, including ToC, Search, linked Glossary, Index, breadcrumbs, etc... and that it did so without need for a server.
>>>
ToCs, Glossaries, Indexes... all that can be done (at least manually) with straight HTML (which is pretty much what Dreamweaver is, just a word processor-like interface for creating HTML).
The software companies that were all trying for their own proprietary versions of web-based help systems have really missed the boat... I know 10 years ago features that output to straight, basic HTML would have been useful. Now they are critical. For example, you can set all those things (but search) in your Framemaker book, but even RoboHelp won't let you output it to a straight HTML format, you have to use all of RoboHelp's custom scripting files are part of the project. The worst thing about those files is the amount of project bloat - when help is stored on a web server or installed as part of an application it may not be as critical, but when you start talking mobile devices with non-expandable hardware resources, that kind of bloat is unacceptable. One would think Adobe could get all their product teams on a conference call to figure out how to get something like Frame to Dreamweaver output, but that hasn't happened yet (that I know of).
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-