7 things you must know about ePublisher Platform

  1. Content is king. Your source content can be Word, Frame, or DITA. You can even import convert other formats such as RoboHelp to Word or Frame and go from there.
  2. Formats are separate from content and can be customized.
  3. Combining content is allowed and even encouraged. Mixed content is just fine.
  4. There are great demos (over an hour’s worth) on the Quadralay web site.
  5. ePublisher has an extendable XML adapter. This extensibility means that no matter what XML you’re putting in, ePublisher can be extended to understand it.
  6. You can automate the dickens out of your output build processes and integrate with development’s version control systems and build with the Auto-mapper.
  7. The WebWorks Wiki (uses MoinMoin engine if you’re wondering) has lots of information and they encourage people to contribute to it.


  • November 13, 2007 - 1:35 pm | Permalink

    Nice write up Anne!

    I would like to clarify our RoboHelp support. Yes, in theory, ePublisher could support RoboHelp as an input. At this time, we do not have RoboHelp input available in productized form for ePublisher 9.3.

  • November 13, 2007 - 10:40 pm | Permalink

    Hi Ben, thanks so much for popping by and leaving a comment!

    I guess I got too excited about King Content. So, to clarify, the idea is to import (actually convert) the RoboHelp content to Frame or Word and go from there. Good deal.

  • David Knopf
    November 17, 2007 - 6:11 pm | Permalink

    Right. That would be the best idea: to convert the RoboHelp content to Frame or Word. Once. Going forward, there wouldn’t be any need to have RoboHelp in the mix.

  • mat
    December 13, 2007 - 9:51 am | Permalink

    Hello there,

    I’m using webworks 7.0.5, not supported apparently and I’m trying to figure out whether it would be a good idea to switch to robohelp 7 instead since it is now supposed to be “integrated” with framemaker (also using that as source of course and would be planning to upgrade to framemaker 8).

    I read somewhere that with robohelp you have to create a new project everytime, whereas of course with webworks (now epublisher), you can stick with the same project and re-generate it over and over again (that’s what i’m used to doing). Do you know whether this is true or has robohelp 7 solved that problem now?

    Also (while I’m at it) how does robohelp deal with javaonline help output? good stuff?

    thanks for any answer, advice, etc… and happy xmas!


  • December 14, 2007 - 3:45 am | Permalink

    Hi Mat

    You don’t need to re-create the project in RoboHelp. With Adobe Technical Communication Suite, you can Update your FrameMaker books added as live links in RoboHelp with a single click. RoboHelp also publishes to JavaHelp format.

  • December 17, 2007 - 9:43 am | Permalink

    Hi Mat and Vivek, thanks for stopping by. Mat, I really haven’t used RoboHelp for a few years now so I’m not sure of the answer, but I’m glad Vivek could give a quick response. He has some blog entries with videos demonstrating much of the RoboHelp 7 product which might also be helpful for your evaluation.

    This tool evaluation stuff sure is easier with blogs and the Internet, isn’t it? But you still have to figure out a lot by prototyping with your own content and then deciding. πŸ™‚

  • Curtis
    May 16, 2008 - 10:32 am | Permalink

    We currently use Robohelp 6 but when doing a search, in many cases you don’t get anything or something remotely associated with the search request. Is this a robohelp problem or something the user can improve? Is there any tool that works as well as google for example?

  • May 16, 2008 - 1:43 pm | Permalink

    Hi Curtis – I’m not super familiar with RH6, but your question might be related to a change from natural language search to keyword searches. See http://www.adobe.com/devnet/robohelp/articles/rhserver_06.html
    The Natural Language Search facility of older versions has been replaced. The new full text search facility is an important change for those upgrading from an older version of the RoboEngine. The natural language search concept seemed like a good idea years ago, but never caught on because users were more familiar with keyword searches. Since the natural language search technique often confused users, it has been replaced.

    Does that help?

    At docs.imis.com, on our search tab, you can see a Google search implementation that my coworker integrated into our helpsite… I’m not familiar enough with Robohelp to give you instruction or even assurance it could work for you, but we’ve found it to be a great solution for our search needs within a help site.

    Hope this helps!

  • Leave a Reply