Last week, I spoke at, and attended, Madworld 2016, the conference hosted by MadCap Software for its users. Here is a summary of what I saw and heard on the second day. These were mostly for advanced users; I didn’t see any of the presentations aimed at new users of Flare.
Once again, I enjoyed immensely Madcap Software’s MadWorld conference in San Diego.
This was Madcap’s second annual conference, building on the success of MadWorld 2013.
One of the main benefits from single sourcing is the ability to reuse existing content. Different departments can avoid duplicating work, which means they can save time and money.
Unfortunately, it can be difficult to quantify these savings before you move to an authoring or content management system that enables you to single source. Analysing all the existing documents in a business can be overwhelming, which means often organisations only quantify the savings after the single sourcing content management system has been implemented.
There are a few software applications that can help you analyse your existing content and determine how much duplication exists. You get a sense of how much time and effort was wasted in the past, which is a pretty good indication of how much waste you’d avoid in the future.
With the imminent release of DITA support in MadCap Flare, will competing Help authoring tools (HATS) suddenly seem inadequate to the task of technical writing?
Where does this leave Adobe’s RoboHelp?
I suspect it will be difficult technically and commercially (Adobe also owns FrameMaker) for Adobe to add DITA support into RoboHelp.
If writers are collaborating on a project or if a Help system needs be localised into foreign languages, then RoboHelp and other HATS may well lose out to Flare.
However, if a sole author just needs to write a straightforward Help File, then many may not feel the need to change from the tool they use today.
So what would you do if you were Adobe?
I wonder if Adobe will choose to compete with MadCap in other ways. RoboHelp could become more of an online training, performance support, tool. Also, Adobe could bundle RoboHelp with FrameMaker at a price that makes Flare seem very expensive.
This, of course, may be all academic if the DITA standard isn’t taken up by more authors.
We took a quick look at Google’s new Chrome browser this morning. MadCap’s Flare Web based Help seems to work fine, but there seems to be a problem with RoboHelp’s Web Help – specifically the Table of Contents.
We dragged some old RoboHelp 5 generated Web Help files into the browser, and we looked at some of the examples listed on Adobe’s Web site (http://www.adobe.com/products/robohelp/customer_examples/). We haven’t had a chance to do any further testing.
Update – The problem is also there with RoboHelp 6 generated Web-based Help.
With the recent releases of new Help Authoring Tool versions for RoboHelp, AuthorIT and Flare, plus the release of Quadralay’s ePublisher 9.3, does this affect which Help Authoring Tool you should purchase?
What I find interesting is the different ways in which the tool vendors perceive the issue of creating user assistance. If you want to create great online Help, with paper being a secondary consideration, you will probably prefer RoboHelp or Flare. If you have a team of people writing, you will probably prefer AuthorIT or ePublisher. If you need to translate the content, then all four of these tools have strengths in their different ways. If you want to generate XML, then Flare, ePublisher or AuthorIT.
The best approach is probably to create a statement of requirements for your situation and then use this as a benchmark when considering each tool. Here are a few factors to consider:
The need to localise content.
How many writers will be involved.
Whether you are creating new content or re-using existing content.
If you need single or multimedia output.
Your view of users and the feedback they might provide.
How much content you might be able to re-use.
Version 3 highlights (from the press release):
Source Control Integration
– Direct integration with Microsoft Visual Source Safe and Microsoft Team Foundation Server
– Integration with most other industry source control systems (that use the MS SCC API interface)
– Faster server-side search
– Searching of non-HTML content (MS Word documents, PDF files, etc.)
– Automatic runtime merging of projects without any in-project work
– Auto-merged search functionality
– Auto-merged TOC options
Advanced FrameMaker Import and Support
– Pass-through marker support (pass raw content or data from FrameMaker to Flare without any processing or modification)
– Drop-down support
– TopicAlias marker support
– Hypertext Marker / Jump to Named Destination support
Enhanced Style Support
– Expanded table print styles for more control when sending output to MS Word, FrameMaker, or PDF
– Optional basic Style Editor for the new user
– Import styles
– Search highlight styles (customize search highlight colors)
– Carrot tag neighborhood markers(a new method for working with inline formatting when necessary)
– New TOC grid view provides more control over TOC editing
– New customizable columns for various Flare interface screens
For a full list of new features and enhancements in Flare v3,see: http://www.madcapsoftware.com/products/flare/features.aspx#v3
MadCap Feedback Service is also now available. With the Feedback Service. Now you can get feedback on how your audience uses your Help content, maximizing the effectiveness of your documentation.
This course will be delivered later this month by Cherryleaf’s Carol Johnston, who is now a MadCap Flare accredited instructor. There’s 8 delegates – some familiar faces, plus a few people we’ve never trained before.