Our Adobe RoboHelp Server legacy
Something strange has started happening recently. People are interested in how our users use our help. What’s more, we’ve been able to answer most of their queries! What’s going on?
Mispellings, synonyms and Robohelp Server
Users of Adobe RoboHelp’s synonym feature will know how useful it is. In a nutshell it ensures that users searching for content in your help file find it even if the entered keyword does not exist. This has many practical uses. For example alternative spellings (e.g. UK versus US English) and terminology that can have different values (e.g. a configurable application where users call a record a “Contact” or “Animal”). With the addition of Adobe RoboHelp Server they have another use.
WebHelp / WebHelp Pro output. Where do I start?
A short while ago a few RoboHelp power users and I had a conversation about the start page used in WebHelp Pro output. It turned out that things were not quite as simple as we first thought and that with WebHelp Pro output things worked slightly differently from WebHelp output.
Where RoboHelp and RoboHelp Server users collide
As a user of RoboHelp Server in a team of five writers spread across three locations, we occasionally come across minor issues with its use. One of those is how we manage the publish process from our RoboHelp projects.
Under the hood of the Robohelp Server
I can absolutely understand why the word “Server” sends shivers down some Technical Writer’s spine, but with RoboHelp Server application there really is no reason that it should. One of its major advantages is that it manages to transcend the Technical Writer and Server Administrator divide. OK there is still some server related detail behind the scenes, but the RoboHelp Server interface manages to bring the important stuff to the surface and display it in a friendly Windows interface. However if you are someone like me, you’ll want to know some of this server side detail. If so, read on.
