This content has been marked as final. Show 15 replies
Hello, and welcome to the RH forums. I can't tell you how on time this is. While they might not know it, it is a solution many have been asking for, for some time now.
For those wondering, a wiki is: "A website or similar online resource which allows users to add and edit content collectively." - source. It is a knowledgebase, much like RH's Webhelp, that allows for user contributions, version tracking, and more. MediaWiki is probably the first, and was developed specifically for Wikipedia.
I've been asking on the http://www.wikimatrix.org/ forums this fall about importing whole directories of generated files (RH output files, to be specific) for either MediaWiki or Twiki. Got a few answers, all requiring master's degrees in wiki development. I wasn't ready for a whole new discipline. I figured I'd tackle it when I got there.
So, it is the large-scale answer to those help authors who ask, "How can my clients add content to the finished RH knowledgebase?". Once converted and imported into your existing MediaWiki project, (using Jason's tool, of course), it is no longer a Robohelp project, but part of the wiki... All subsequent editing occurs within the wiki itself, although it does look like Jason's thinking about subsequent RH uploads as well.
I really like the image history capabilities, and being able to follow changes using the RSS feeds on the recent changes page. And yes, Jason, any further developments will be heralded and appreciated; comprehensive markup, version control and GUIs are all great.
Nice work sir, and an outstanding contribution for the content management and single-sourcing crowd...
My team might be very interested in this tool (or a similar one). We have a lot of internal information that we have maintained for years as a help project. Lately we have been itching to convert it to a wiki, in order to make it more accessible and easier to update. However, we wouldn't like to lose the formatting. Maybe we'll wait for the next version. :-)
Thank you for the kind words.
I would like to add the natural connection between RoboHelp and MediaWiki to your excellent summary of Wiki’s. Both are topic based providing a straight-forward 1-1 match. In contrast, many Microsoft Word documents (or any text document) first need to be transformed from a “document” into “topics within a document”. I have found when importing documents to RoboHelp, I need to do a lot of preliminary work in determining which header level is the right starting point and then correcting the exceptions.
Some of our formatting decisions were done to make it easier for people to edit the Wiki once converted. For example, we simplified the table conversions to remove complex formatting avoid inside formatting, nested tables, split inner rows/columns into multiple cells, etc. MediaWiki does not encourage the use of sophisticated table structures instead it encourages simple layouts to better enable collaboration. This was fine for us, as our goal was to get content to the right people with tools to edit and contribute.
Why not try converting one set of internal information to the Wiki as a test and see if your users miss the extra formatting. If they do, let us know what is important and we will see what we can do. Or if you like, please feel free to modify the code and we will validate, test, and re-release.
RoboHelp2Wiki Version 0.9 working with Robohelp Version 6.
As far as we can tell there were no changes to the XML tags or the directory structures using Version 6 XML Output handler. The project meta data in the project files are also practically the same. I did test the new user defined global variables feature worked and they worked and converted correctly to MediaWiki.
This is fantastic! Now we need a Frame2Wiki...
I seem to be lagging behind the trend -- again.
Oh well, nevermind. Does anyone know where I can find the robohelp2wiki.zip file? The mediwiki page has lots of information, but I cannot see a link to a download for the tool.
I'm starting to look for information on why and how I might use XML output -- how and where it's deployed, how the end user gets there, what's needed to open it, and strategies for building the output to take best advantage of the form.
RoboHelp2Wiki sounds interesting, and I want to try it.
RH online help has some basic how-to instructions and explanation, but I need more to be able to understand how to use RH2Wiki.
I have tried to post all the information required to run and understand RoboHelp2Wiki on it's MediaWiki Extensions page:
Was there something specific that you needed?
Just wondering if you've tested on RoboHelp 7 yet?
Thanks. It happens that your site is flagged as a discussion forum, and, even though it's in the Business/Technical category, my Internet Police are blocking access.
I have a channel for appealing -- they look at site-by-site requests -- and it may take a day or two.
The question is not so much about the Wiki as my need for some basic education on how and why RH XML output is used. Then I can start getting a handle on Wiki Servers, etc.
7? I thought at first you may have mistyped and meant 6. That must have been a stealth launch. I will download a trial version to test and check out the latest release.
We have tested to RoboHelp 6, JRE6 and MediaWiki through 1.11.0
We picked RH XML as it was the easiest to parse when converting to another format. Our source code is in the download, which may help in the learning process.
Does this work by any chance with RoboHelp8? Or is there any possibility I could upload the chm file to the wiki as it is? Or maybe in a WebHelp format? Just add it to one of the pages?