With more than one person working out of our content sets, we would have had a hard time tracking versions if it weren't for Flare's TFS integration.

Within a couple days, we were able to deliver a customized user manual as a Word file, so the user could make additional changes. Before we had Flare, this wasn't an option.

We also like the ability to customize our content with Flare. We have two sets of users, developers and end users, so we maintain two different content sets to support their needs. We also need to publish to Word, PDF files, the Web, and mobile, and Flare lets us do that all from the same project.

Flare offers a way to develop better documentation and online Help without having to shutdown and re-engineer the processes you already have. Businesses need tools like Flare.

We use Flare to create a very user friendly cascading presentation of information where the content moves deeper and deeper into a concept, and we add links to videos and other content to enrich the customer’s experience.

I have used other source control systems with Flare, and they have each had their challenges. The MadCap Central solution is so easy and works so well – I think it’s a no-brainer!

Migrating from FrameMaker® to Flare made more sense to me than I expected. Flare simply makes it so much easier to control content, it’s more versatile, it’s more open to the outside world (XML), and if all goes wrong I can use Notepad. It caught the attention from the company developers (that’s a first in 30+ years) and the MadCap guys win hands down on service and support (that’s easy since the Adobe support is close to nill on FrameMaker®).

We are using MadCap Flare for most of our customers projects. Some are still working/requesting Word or FrameMaker, but there is hope to migrate them to a "real" technical writing XML tool.

With MadCap Flare and Capture, we now have a central source for content and high quality screen images, whether we publish in print or online.

I have been working with Flare since its inception, and I’ve also taken CSS online courses, yet I still learned a lot from this class with Scott. It was well worth taking this class.

EMPI is delighted to collaborate with MadCap and train students and professionals in the field of technical writing. This is just the beginning, and at an appropriate time we will be looking to set up a centre of excellence dedicated to technical writing.

With Flare, we were able to create our first mobile Help implementation in less than two weeks, and single-sourcing allows us to update all of our Help formats, including mobile, concurrently.

MadCap support is fantastic. The key thing that I appreciate is that the support team gets back to us in a timely manner, so we can remain on task and on schedule.

MadCap Flare offers a complete solution that is able to meet authoring needs at all levels of complexity. Its true single-sourcing capabilities, reuse features, and user friendly interface make it a tool that students and professors will enjoy using. When we heard about the MadCap Scholar Program, we knew from the very beginning that we wanted to be a part of it. We’re excited to team up with the industry leader in technical communication and authoring software, which gives us the opportunity to teach students how to use a modern professional tool. This practical knowledge will play a key role in their success in future careers.

True to its promise, Lingo enabled translation while preserving all of our document structure and formatting, and my translator reported back that this is going to make her job much simpler.

I have been a technical writer for twenty-six years and was a technical editor for seven years before that. The MadCap technical writing team does great work. I have worked with the Flare product for about seven years and love it, but I have no end of praise for the tech writers because theirs is among the best product documentation I have ever seen. When MadCap talks about its excellent tech support, they should always mention documentation.