One of the questions I get asked from technical writers and content managers is whether or not they should move to Madcap Flare. Many of you will have already invested time and energy in RoboHelp (when it was owned by Macromedia), and now that it is part of the Adobe family, may have some thoughts about its long term viability. RoboHelp was, and still is, a great product. But Flare has a lot going for it to. Here are few reasons you should save your RoboHelp budget and upgrade to MadCap Flare.
|
ISBN: 0615141455 |
MadCap Flare for RoboHelp Users1) The workflow of MadCap Flare is similar to RoboHelp but better
MadCap Flare is designed from the ground up by some of the former RoboHelp product experts. The workflow is intended to be very familiar to RoboHelp users to ensure a low learning curve. It includes many unprecedented features as well as a cleaner, more user-friendly interface.
2) MadCap Flare uses industry standard mark-up
MadCap Flare is designed to generate pure, clean, compliant XML. There are no proprietary tags, no editor tricks, nothing to interfere with your existing XML workflow or cause conflicts with future tools.
3) You can leverage your existing RoboHelp projects
MadCap Flare allows you to import your existing RoboHelp projects, so you wont lose legacy content.
4) MadCap Software is committed to supporting converted users
MadCap Software will offer generous support incentives to customers who currently subscribe to a RoboHelp maintenance plan but wish to convert to MadCap Flare. Additionally, we will offer complimentary support to assist you with importing RoboHelp projects into MadCap Flare.
What’s your thoughts?
Is it worth making the switch to Flare? Or it is better to stick with RoboHelp?
Need help with your web writing? Click here for a Free Quote
