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!
My previous article was about choosing the right eLearning authoring tool. But now comes the hardest part—starting to work with it, even if you worked with similar tools before. Here is a short glossary of general and tool-specific terms to help you get eLearning done in leaps and bounds. The tools covered in my glossary include Adobe Captivate, Articulate Storyline, Lectora Inspire, and TechSmith Camtasia.
As advertised, Piktochart is a really easy-to-use infographic maker.
The story goes: I, an Information Developer, was asked to prepare a Case Study, quickly and in the form of an infographic. Sounds typical. But the branding dictates colors, size, opacity, and styling. Sounds like complex editing. Cheerful me took the friendliest tool and now can share my personal lessons learned.
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?
Insightful article covering the following important aspects:
- What is Markdown?
- How and where to get started with Markdown in documentation?
- What points to consider?
All things considered, let’s put it that way:
Whereas Markdown is much simpler than HTML or any other markup language, it may introduce a lot of mess to documentation with complicated structure.
On the other hand, it may be quite enough to create simple docs (like, say, Release Notes) on a project.
What do you think?