MadCap Software Sponsors the Tech Writer Voices Podcast
You may be wondering exactly what sponsorship involves. Basically, it's different for each company, but I'm offering promotion on my podcasts in exchange for a free copy of the company's product. This is actually something that Heidi Hansen, my co-host, encouraged me to do long ago.
So for the past week, I've been exploring MadCap Flare Version 3.1 with a lot more depth than I explored the trial version of the 2.0 release last year. I'm thoroughly impressed with Flare. It provides a robust, functional online help tool that simply works. When I say robust, I mean it. The granularity of the style editor is powerful -- allowing you to create stylesheets for both online and print formats.
Some other things that stand out:
- The generated output to print actually conforms to the styles you configure in the style editor.
- The conditional tagging is intuitive and easy to apply.
- The net DotNet format allows you to deliver context-sensitive help that is embedded and dynamic.
- The Webhelp skin is easy to customize.
- Flare's built-in help is excellent -- no need for a third-party book to guide you through the product.
Although some aspects aren't as obvious as I hoped, Flare is a tool that I won't easily grow out of. And their expansion into other areas -- screen capture, audio, translation, screen demo, and more -- makes their product suite compelling. In some ways Flare is similar to RoboHelp, and in many other ways it's completely unique.
I know I sound like a marketing brochure, so I will admit one thing I don't understand about Flare. A new feature of Flare is Easy-Sync, explained as follows:
A first in the industry. Flare supports two different work flows when importing Microsoft Word or Adobe FrameMaker documents. With the standard import you can leverage existing content and then continue your editing and maintenance using Flares built in editor. However, with the new Easy Sync capability you can have Flare treat the original Word or FrameMaker document as the source file. This allows you to do all of your edits and maintenance in the original Word or FrameMaker document and still get all of the powerful publishing capabilities of Flare. The first tool in the industry to support two different work flows within the same product.
What I don't understand is why anyone would want to maintain a source file in Microsoft Word and then publish to an online help format. Flare's online help editor is so much easier to format and manipulate content than Word. Working in Microsoft Word and publishing to online help seems backwards.
The only logic I see is that some authors may prefer Word due to their familiarity with it.
MadCap's pace is impressive, and the sophistication and functionality of Flare is astounding considering that the product is less than 2 years old.
Look to some upcoming podcasts dedicated specifically to Flare and other Madcap products.
By the way, are you a Flare user? I'd be interested to hear your experiences with it or any other Madcap product.
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.
If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.