This content has been marked as final. Show 7 replies
I'm not sure that I'm on the same wavelength, but I would be VERY interested if such a tool allowed me to turn my very large RH project into a wiki that selected users could contribute to. My worry is that I've used RH to create a lot of dhtml effects (e.g. popups and layers) and I don't see how most users could edit this without using a tool that is at least compatable with RH (and themselves being fairly sophisticated RH users).
That would bring the RoboHelp/MediaWiki conversion full circle, wouldn't it? It would also allow true collaboration for many authors on a single Robohelp project. Sweet. The Content Management fans will be totally jazzed.
Jason was talking a bout a Wiki2RoboHelp module; he's announced a RoboHelp2Wiki tool already: you can see his original post at:
it's all good!
I have a similar problem with publishing to pdf: I like the idea for the security it offers. Unfortunately, the only choice is to convert everything to normal text (popups, expanding/drop down text etc.).
It's true, but wikis, and projects most suited for conversion to wikis, are usually content-focused.
When multiple authors collaborate on documents to get the best of their collective knowledge, layers and popups are not a high priority. Those DHTML bells and whistles are usually among the last of the tweaks to a help system. Content usually comes first.
I truly understand your concern. As a software product manager (and writer), I do know that sometimes it is not always all about content. Good presentation is required. Popups and other effects are necessary to focus end users and get points across.
Doug Worsham may have summed it up the best (paraphrasing) ..On a Wiki Content is more important then form. This is remarkable because Wiki’s becomes information rich. This is unsettling because Wiki’s are not pretty. ..
With respect to this project, I do not foresee users contributing effects in the Wiki. I expect them to add new content and then when done the information is converted back to the HAT. We as editors and writers then add the effects to produce the new completed documentation. For example, consider converting documentation for a Version 1 from RH to the Wiki. Developers update the Wiki as they work on Version 2. When complete the Wiki is pulled back into RH. Part 1 is done in RoboHelp2Wiki.
Jason, your idea makes a lot of sense. You've convinced me to take the plunge and try out your tool for my project. I Thanks.