Ray Davis

Regulatory agencies often insist on PDF or paper user documents. These instructions-for-use tell a user how to safely and effectively use a system. But there's only so much you can do with a PDF to make it accessible: a table of contents, an index, and the search capabilities that are limited by the viewing application.

Once you convert your document to a responsive HTML, a whole new level of accessibility opens up to you. Flare's ability to single-source a document lets you create two separate documents from the same source. You can create an HTML document that is searchable, accessible, and well-organized that actually supports your users; and a separate PDF to satisfy your regulatory agencies.

Learn our tips and tricks for organizing your document to maximize both your PDF and HTML output, and learn how to argue that these are actually the same document.

If your technical writing department has been around a while you have legacy documents, some that may date back to the stone age of technical writing. A common tool for these legacy documents is Adobe InDesign. Now that you've decided to modernize with topic-based authoring, the problem is that there is no direct path between those documents and Madcap Flare. We all know the axiom garbage in, garbage out. The quality of your input directly impacts the quality of your output. But Madcap Flare lets you change that outcome. Garbage in, golden out.

You'll learn how to move those InDesign documents to Flare, what do you need to do every step along the way to minimize re-work, and how to set up your Import to get the golden result you want.

Finally, we'll learn where to look for re-use, and how to manage this change both up and down your management chain.

You don't have to be stuck with a tool you don't want to use, and we'll show you how to get there.