Today we have another guest blog post from MadCap Software, written by Jose Sermeno, a product evangelist at MadCap. As the scale, complexities and deliverables of technical communication content have evolved, authors and content creators have an ever-increasing arsenal of software tools at their disposal. “Single Sourcing,” “Visual Editing,” and “Multi-Channel Publishing” are all buzzword functionalities one can now expect from a modern technical communication tool. As “features” they’re easy to describe—but providing users with an interface that is easy to use and representative of the underlying structure or styling of the content, without overloading them, is a challenge. Our blog post today is going to cover some of the ways MadCap Software has placed particular emphasis on providing users with a clean interface that provides both assistance and content structure insight while creating content. Figure 1. Flare v9’s XML Editor Figure 2. XML Editor Local Toolbars While users are presented with an ever changing set of interfaces and editor rules from tool to tool—people generally have an existing set of references from their experiences with word processing or publishing software. The popular Ribbon from Microsoft for document editing and formatting, dynamic dual screen editing from tools like Dreamweaver, and the colorful (and useful) syntax display in a text editor like Notepad++ all represent editors designed with a focus for developing a specific end result in mind. In Flare, we’ve tried to include only as much information as the user will find necessary in their development. With that said, every marker in Flare can be disabled, based on the user’s preference. We’ve always considered our editor to be a unique and distinguishable strength of Flare, and with version 9, we have made some significant updates with efficient authoring and ease of use in mind.