MadCap Flare: pain points and solutions (part 2)

Using MadCap Flare, a help authoring tool, can be cool and unbearable at the same time. Those InfoDevs who deal with it on a regular basis will definitely understand what I mean. The more I work with this tool, the more I learn about its capabilities and pitfalls. The work on multiple print outputs and the HTML5 target makes the challenge even more exciting. Previously, I shared some issues I encountered with possible solutions for them (See MadCap Flare: pain points and solutions). In this article, I have prepared another portion of troubles to be considered.  So, Ready Steady Go!

Continue reading

Advertisements

MadCap Flare: Issues and Fixes

MadCap Flare. We, Technical Communicators, use it daily. But do we really use it to its full potential? Or, maybe it has some hidden capabilities or mysterious forces we may have no idea about? Let’s follow this bumpy journey and find out together! Continue reading

How to use custom fonts in TopNav help

Imagine a situation: you’re going to prepare a help system for a website. You suggest creating a help that has the look and feel of the website itself. The customer is happy with that, and you’re eager to start as you have MadCap Flare 11 or 12 with that cool TopNav output. However, the website uses custom fonts, and you need to use them in your help system.

What would you do?

Continue reading

It's a dangerous business, Information Developer, sending out your portfolio. You create a sample, and if you don't keep your NDA, there's no knowing where you might be sued off to