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!
I work with the MadCap Flare tool on a regular basis. Namely, with two targets – the HTML 5 Help system and the PDF file. That presupposes that I deal with two outputs, two style sheets, and all my troubles are usually multiplied by two :). In this article, I want to share my pain points as well as possible solutions for them. So, here we go!
Do you spot flaws or imperfections others do not see? Do you place high demands on yourself and people around you? Do you set extremely high standards? In other words, are you constantly striving for perfection?
If your answer is YES!, then welcome to the club of perfectionists.
I started my career as an Information Developer not so long ago. I never worked in the field of technical communication before and never thought that someday I would give it a try. So, as Bryan Adams sings, ‘Here I am, this is me’. I have not acquired any extensive experience yet, but still, I think that I can share some discoveries made during my debut in this position.