Archives

On Wednesday at the MadWorld conference, I join forces with the indomitable Daniel Ferguson for a presentation on advanced TopNav output.

Session Description:

You already know that MadCap Flare is the best tool to help you create a great experience for your users when they engage with your help system online. What if you could make it even better? Turn those ideas into action by attending this advanced workshop where we’ll show you how to use bleeding edge CSS3 with complex selectors, pseudo classes and more to make your output “sizzle”. We’ll talk about how you can integrate JavaScript libraries like jQuery and Grunt to do more to make your output shine above the rest. Flare trainers Paul Pehrson and Daniel Ferguson join together in the workshop to not only show you what is possible, but to give you the tools you need to try it on your own. You’ll leave with specific ideas of things you can do in your current projects to make them better for your users.

In-Class Files

Click here to download the sample project and JavaScript files:

MadWorld-AdvTopNav

 

In case you missed it, MadCap Software announced that due to the success of the annual MadWorld conference in San Diego, they are adding a new conference in Europe, MadWorld Europe.

The conference is scheduled for September 11 to 14, and will be held in Prague, Czechia.

If you are interested in presenting at MadWorld Europe, a Call for Papers is open until Jan 23rd.

Read more about it on MadCap’s blog:

Conference Update: MadWorld Europe 2018 Announced, MadWorld 2018 Registration Discount Ends Dec. 31

When you are working in Flare, you may have encountered an issue that drove me crazy for a long time regarding snippets.

When you have some content in Flare that you want to convert to be a snippet, usually you can just select the paragraphs of text and click the Create Snippet button on the Home ribbon. However, if that selected content contains certain types of content (I’m looking at you, tables), the Create Snippet button isn’t available. So what should you do?

One option is to select the content, cut it to the clipboard, go create a new snippet file, then paste the content into the snippet file, and finally insert the snippet into the original topic. Don’t do that anymore.

Instead, when you have the content highlighted, press the Tab key on your keyboard, and from the pop-up window, select “div”, then click OK. Now, click on the div structure bar. The Create Snippet option is now available! Click it to convert your div’ed content into a snippet.

Tip: If you can’t press the Tab key because you are in a table or a list, use the  (group) button instead.

You can stop here if you want, or you can make the following additional change. In the new snippet file, right click on the div structure bar, and click Unbind, then save the snippet file. This removes the div HTML element from the content. It doesn’t hurt to leave it in; since the div doesn’t have an id or class it won’t change what the content looks like in the output. That said, there is no reason for it anymore, so you can delete it if you want to keep things clean.

There you go. It’s Wednesday, but we’re going to call this a #FlareTipTuesday anyway.

Hey all,

I’ve been talking with a good friend of mine about launching a Flare-specific podcast. We would include interviews with luminaries in the Flare community, tips and tricks in working with Flare, a broader discussion of technical writing in general, and other such topics.

To get started, though, I’m interested in hearing from you about what topics you would be interested in listening to. What kinds of questions would be best answered in a podcast format? Who are the people you’d like to hear from to learn their perspectives on help authoring, and on using MadCap products?

Feel free to submit comments to this thread, or you can use the comment form.

I look forward to hearing from you.

A recent post in the MadCap forums addressed the question of putting a mini-TOC-like object at the beginning of a topic to show all the headings on the actual page.

In the past, I (like many of you, I assume) have tried to do this using a mini-TOC proxy in Flare. We then discovered that the mini-TOC proxy only shows TOPICS that are beneath the current topic in the TOC that this topic is a part of. In essence, a mini-TOC proxy is useful at the beginning of a chapter, so you can point out all the topics that are in the chapter. Among other things, this gives you content on the container topic in the TOC that begins the new chapter, which makes breadcrumbs and side-menus (in TopNav output) work.

The problem is that this doesn’t actually answer the original question. I want a dynamically-generated list of headings that are in the current topic.

Flare Maestro Dave Lee gave a brilliant answer that I had to share with you. He wrote a script that you can use to generate this list automatically for a given topic. You can read his solution here.

The only thing I’ll add to Dave’s answer is the idea that you might not want to have this feature on every page in your content; maybe you want to apply this to specific pages or types of pages in your documentation. In that case, you’ll want to create this in its own masterpage that you can apply to topics that should use it. That way it isn’t an all-or-nothing decision.

Dave Lee blogs about MadCap Flare, and specifically about scripting hacks he’s created for Flare at https://ukauthor.wordpress.com/. Check out his site for other cool scripts you can add to your Flare projects.

I had a recent comment on a post I wrote nearly ten years ago. The post actually earned me a bit of notoriety in the MadCap community. For many years after writing that post, people would see me at an industry conference and say, “Oh, you’re the guy who wrote The Six Things I Hate About Flare.” I would quickly correct them, telling them I was very careful at the time to not use the word hate. In fact, right after my actual post entitled “Six Persistent Flare Problems,” I quickly published a post on “Six things I loved about Flare.” I published in that order, because I wanted people to remember the great things I said about Flare, not the quirks that annoyed me. (Nobody ever commented to me about the latter post though, so that didn’t really go as planned.)

A lot has changed in ten years! As I reread that post I realized that ten years ago, I was using Flare version 3. Since then, there have been annual numbered releases, all the way to Flare v12. Then MadCap changed the release naming scheme, and moved to a year-based name, so we got Flare 2016 r2, which could have technically been called Flare 13, but now MadCap posts the year of the release, and if a new major release is released in the same year, they add the “r2” addendum so you can see what version you’re dealing with. That means with Flare 2017, there have been 11 major release of Flare since my “persistent problems” post ten years ago. That is a lot of time, and A LOT of new features.

Now I am using Flare 2017. For your sake, I hope you are using Flare 2017 as well. I’ve been using it since it was released in January, and I’m exceptionally satisfied with the new features in this release.

In the past, I’ve talked in detail about the new features in a given Flare release. I think in this post, I want to take a slightly different direction and talk about my overall satisfaction with Flare as a technical writing tool, based on over a decade of experience working with Flare, training on Flare, and presenting on Flare to large audiences around the world.

Let me state my opinion right out of the gate: MadCap Flare is hands-down the best help authoring tool I have ever used. Its list of features is extensive, and the breadth and depth of its features is vast. The power of Flare is in its ability to help you reuse content in many different ways. You can write once, and maintain content in one single location, and then use that content in many different ways for many different audiences. Here is a partial list of single-sourcing features in Flare 2017:

• Conditions – You can apply conditions to content, and then you can select a combination of include/exclude commands for conditions for each target that you build. (In the context of Flare, you can consider a target as a deliverable. It is a specific set of content published for a specific audience.)
• Snippets – You can reuse chunks of content endless times across your project by putting shared content into snippets, and then referencing those snippets when you need them in other topics. When you need to make a change, you open the snippet, and the content is automatically updated everywhere you use the snippet.
• Variables – Flare has support for several types of variables, allowing you to specify at the project level, or at the target level what the text of a specific variable should be. This makes it easy to create separate targets for specific customers where you can using the wording and terminology that is specific to that customer. Variables are also useful for items that may be used across the document, but may change over time, like the version number of the product you are documenting.
• Snippet Conditions – An advanced feature in Flare, snippet conditions let you customize a snippet for use in multiple places in the project where the content is similar, but not exactly the same. You can then edit the conditions that are used for the snippet at either the topic level (all snippets in that topic will use the specified condition), or at the point the snippet is inserted (allowing you to use the same snippet in multiple places in the same topic, but with different conditions applied.
• Snippet Variables – A fairly new feature, you can specify the variable text of a variable used in a snippet at the point of insertion, allowing you to set custom text at the point of insertion without having to specify the actual text in the variable definition, making it easier to use a snippet in multiple ways across the topic or project.
• Multi-channel publishing – A Flare staple since the beginning, the number of ways you can publish content is increasing over time. Flare now supports  two flavors of HTML5 publishing, both a traditional tri-pane output and a new “Top-Nav” output that works more like a traditional website. Other targets include direct-to-PDF publishing, XHTML targets, DITA, Framemaker, and Word (to name the most popular).
• TOC-embedding – In my experience, this is an oft-overlooked feature in Flare that allows you to single-source your TOCs and embed a TOC into another TOC. This means you can update the order of topics in multiple targets by editing the sequence in one TOC, and all other TOCS that use that edited TOC will automatically update. When you are working in small projects, this may not be too important, but for clients with larger projects (many I’ve worked with have dozens of TOCs; my main current project has 80 TOCs) this is a real life saver so that content in various TOCs don’t get out-of-sync with each other.
• Project merging – In many writing shops, different groups of writers are working on different parts of a project, and at some shops, documentation may be created for separate projects that need to be merged into a single cohesive help system for customers. Flare allows you to merge project outputs, giving you that single system for customers.
• Screen capture tool that uses conditions and variables from your project –  MadCap Flare ships a companion tool, MadCap Capture for free with each Flare license. Capture is a powerful tool that allows you to not only use conditions and variables in your screen shots (and they automatically get updated each time the project is built!), but it also keeps the content of the call-outs separate from the call-out itself, so you can edit call-outs, replace background images, and even translate call-out text easily at any point in the future.
• Global project linking – If you need to work in separate Flare projects, but you have a core group of files you want to use in all your projects (style sheets, master pages, glossaries, corporate logos, etc.) you can maintain those items in a ‘master’ project, and then you can link your other projects to that master project and import those shared elements. Any updates to the master project will get pulled into the other projects before the other projects are built, so they always have the latest-and-greatest versions of those globally-used files.

And that is just a list of Flare’s single sourcing features!

What else do I love about Flare? Lets talk about the user interface experience. Flare is designed with the technical author in mind, and has many, many features that make creating and updating content easy and efficient. For example:

• Customizeable user interface – Flare’s various windows and panels can be arranged in a virtually unlimited number of ways. If you have a wide-screen monitor or multiple monitors, you will especially appreciate Flare’s interface flexibility.
• CSS-based styling – This is huge. Flare uses CSS for styling both online and print output. While you don’t need to know CSS to use Flare’s editors, the work in the background is being stored in CSS, and you can get in and manipulate it manually, so any CSS you learn (or already know) will help you style your content the way you want in Flare. Can’t figure it out? Look at the literally millions of websites and hundreds of books on CSS to find your answer.
• Multiple editing views – One of the things I fell in love with in Dreamweaver many years ago was the split-screen view where I could see the code and the WYSIWYG editor at the same time. (This may be born of my love of ‘Reveal Codes’ from the old WordPerfect days.) Flare fully supports this. You can view just the WYSIWYG editor, or the text editor, or both at the same time. You can put the windows top/bottom or side-by-side. You can filter your current WYSIWYG editor by conditions, allowing you to see only specific conditions while editing. You can view your WYSIWYG window in print format (complete with pages based on existing page layouts in your system), or in web format (where you can even specify a specific media type). There are a lot of options, so you can work in the way that makes the most sense to you, based on the content you are currently working with.
• Dynamic preview – This is a new feature in Flare 2017, and I love it already. I have an extra-wide monitor, and I love having the preview of my content being updated in real-time while I’m working.
• Context-sensitive right-click – Depending on where you are, when you right-click in a topic you get a list of options. In a table, you get table-specific options. In regular text, you get different options. There are easy ways to insert links and cross references without necessarily looking at the entire list of your topics (a list showing, for example, all open topics, which can be quite useful in large projects).
• Drag-and-drop – When you need to insert content from the Content Explorer into your topic, in most cases, you can just drag the item from the Content Explorer and drop it in your topic. This makes it super easy to add content to a topic.
• Customizable keyboard shortcuts – Flare lets you create your own keyboard shortcuts for virtually every Flare function. I have keyboard shortcuts to apply specific styles, and others to run specific Flare macros.
• Quick search – The main project I work on is big. Really big. Finding a specific topic can be difficult. I can use quick search to find any file in the project quickly and easily.
• Quick-access toolbar – Like many Windows products, Flare lets me  customize the quick access toolbar at the top of my screen. I can even select sub-options (like a numbered list) and put them on the quick access toolbar making it very easy to find and use them.

And this is just a very short overview of what Flare can do. We haven’t even gotten into context-sensitive help, reports, the link viewer, group reviewing options, and integration with source control (including MadCap’s own Central offering). In my organization, we have our Flare project connected to GIT, which is connected to buildbot, so every time we check into GIT, buildbot generates a command-line compiled version of our targets, and copies the resulting files to an internal web server. Our developers and help authors always can view the most-recent content on the internal website, making it easy to review and approve topics.

In addition, I’ve had the privilege of being part of the Flare community forums for many years. That is a great group of people with a wide variety of experience and expertise who are willing to help users with questions that they have. The community forums, in addition to Flare’s excellent support staff, make Flare a very attractive tool because there are willing people who want to help you succeed in your project.

Are there things I’d like to see added to or improved in Flare? Sure there are. For example, I’d love to see Capture profiles stored in the Flare project, so they are available to all team members. I’d love to see more robust content management options for replacing live content on a schedule. I’d like to see a browser-based content review tool (taking MadCap Contributor to be a cloud offering) — something that might make MadCap Central a more attractive offering for a wider user base. I’m frustrated with side-menus in TopNav outputs not being location aware (if you have multiple topics used in the same TOC, only one of them is generated into the output, so the sidebar navigation is only correct for the first place the topic appeared in the TOC).  But these are all things I expect MadCap to continue to improve over time.

If we–from the outside–can judge based on the last ten years, it’s a pretty safe bet that there will be a lot of Flare goodness in store.

In the comments, tell me what features you think will be in Flare in the next ten years (Flare 2027(!), if the current naming scheme is continued).

There is a reason I’ve said in the past that MadCap has the best user conference I’ve ever been to. The MadCap team puts their heart and soul into making the conference informative, interesting, engaging, and fun. Such was the case again this year at MadWorld 2016.

San Diego is a wonderful place for a conference. Even when the weather is “bad” by their standards, those of us who travel from the north think the weather is wonderful. Case in point, the day I arrived, my Uber driver could tell I was not from Southern California because I was unashamedly wearing shorts in 70 degree (Fahrenheit) weather, with a chance of afternoon showers.

This year, the conference was held at the San Diego Hilton Resort and Spa. This is the third venue for MadWorld. The first two years were downtown in the Gas Lamp District at the Hard Rock Hotel. Last year, we were housed at the Catamaran hotel. Each location has had its pros and cons. The Hard Rock is in the middle of everything, and you can easily go anywhere. Both years we were there during a baseball game, which was within walking distance of the hotel. Last year the Catamaran was on the beach of the bay, and within short walking distance of the beaches on the Pacific Ocean. Transportation options were more limited at the Catamaran, being a long ways from the Trolley or other mass transit options, but the view was spectacular. The San Diego Hilton Resort and Spa is on the opposite side of the bay, backing I-5, so it was easy to get to. We took several Uber trips to area attractions including Old Town and Little Italy, and the trips were typically only 5 to 8 dollars. The hotel has an exclusive feel to it, and had a beautiful pool with hot tubs, and easy access to the beach. My only complaint about the Hilton is that there weren’t any restaurants within walking distance of the hotel, so if you didn’t want to eat in the hotel restaurant, you had to hire a ride.

As always, the conference featured full breakfast and lunch meals all days of the conference. The food was good, if a bit repetitive (breakfast, at least). If you are from further inland and north, like me, you can’t help but love the freshness and ripeness of the fresh fruit. Each evening, MadCap hosted a mixer event with free food (typically billed as appetizers in the program, but I found the variety and quantity of foods to be quite satisfying), with free drinks.

Monday morning’s keynote presentation was given by MadCap CEO Anthony Olivier with help from VP of Product Evangelism. Together they announced a new MadCap product called MadCap Central. This was the first MadCap had publicly discussed this product, and it looks like it will be interesting. It is a cloud-based tool that will feature project management and source code management. It looks like it will allow you to create roles in your organization, and then control access to edit or publish content depending on a user’s role. This was an early announcement of Central, and we didn’t get to see a live demo yet. I believe MadCap stated that Central will be available later this year. I’m sure we’ll be hearing more about this from MadCap in the coming months, and I hope that even before then I’ll be able to interview somebody from MadCap to give you more information.

As always, I’m impressed by the caliber of presenters that MadCap selects to present at the conference. I recognize that comment sounds a little self aggrandizing, since I was a presenter, but I’m talking about the other presenters there. Every session I attended was well constructed with good content. My favorite session from Monday (from a good list of awesome presentations) was Matthew Ellison’s presentation on CSS Flexbox. If you’ve tried to work with JavaScript libraries to do responsive layout, you will be amazed at how simple it is to use Flexbox. My first week back at work, I was able to wow my boss with a Flexbox based design for a new documentation homepage, using the techniques I learned from Matthew.

One Tuesday one of the presenters learned his father had passed away, and he had to leave the conference early (our thoughts and prayers are with you, Justin and your family). In other sessions, I gave an introduction to web scripting with information on how to incorporate jQuery plugins in your Flare content. Scott DeLoach followed that session with an in-depth discussion on how MadCap uses jQuery, and gave several jQuery libraries that you can include in your Flare projects to extend your existing HTML output. He had some great examples of things you can do including search auto-complete, and a plugin to turn a page into a PDF document.

Wednesday was an additional day of conference for those who purchased the Advanced Workshop. I gave the first presentation of the day on source control, and I have to admit, it was not one of my better presentations. I had been using one cloud-hosted source control provider until about a week before the conference, when I realized there was an integration issue with Flare 12, so at the last minute, I switched to a different source control provider, and there were hiccups in the process. I was grateful that the estimable Daniel Ferguson from SmartOutput (formerly Write Degree Communications) conceded to come up and help me on stage, as he was the one who introduced me to my new cloud provider. I hope we didn’t make source control look harder than it is, but I’m not sure. (It GITs better! — Sorry, bad pun.)

Finally, Thomas Bro Rasmussen announced at the conference the launch of pluqin.com (yes, that is a Q, not a G), a site where he will be selling plugins for MadCap Flare. The first plugin is still in pre-release but it looks absolutely amazing. It is called Style Replacer, and it has some phenomenal features. It will read your CSS file content, and then it will allow you to change all instances of one tag to another. It considers classes, and can even completely unbind all classes of a certain type.

Consider the following: If you have a paragraph style that you are using as intro text to a procedure, you might have code like this:

<p class=”ProcedureIntro”>Adding widget to the system</p>

If you wanted to change all of those, across your entire project to the H2 tag, you’d have a LOT of manual work, if you don’t know how to do regular expression searches. While you could easily search for all the <p class=”ProcedureIntro”> tags and convert them to <h2>, you would have a bunch of broken topics, because you can’t easily search for the correct </p> tag to convert it into a </h2> tag.

With Style Replacer, you can do this across your project very easily. It works on images, list styles, div tags, span tags, and more.

Best of all, Thomas promised that all plugins on his site will only be $30 USD. The time saved by using this plugin on a large find-and-replace project could pay for itself several times over the first time you used it. He says he has lots of other interesting ideas in the pipeline, so be sure to check his site for updates.

MadWorld was another huge success, in my opinion. MadCap does a great job of putting together quality sessions, a great atmosphere, good food, and a fun time. The conference is a great value. Whether you were there this year or not, you should make plans now to attend next year. It is a wonderful mix of “our people” that I have never seen replicated at any other event.

Hey everybody! It’s that awesome time of year when MadCap releases the latest and greatest iteration of MadCap Flare. This year, we’re getting MadCap Flare 12, with a host of new features and enhancements that improve the authoring experience. One of the great things about Flare 12 is that there is a nice mix of features that help our customers, as well as features that help us as help authors create and manage content in Flare.

If you haven’t already, I recommend you peruse the MadCap Flare 12 page on MadCap’s website to see the features that they are promoting in Flare 12.  I can’t possibly comment on every new feature; I don’t have the time, and I’m sure you don’t have the patience (grin), so instead, let me tell you the features that I’m most excited about in Flare 12 with the reasons why I’m excited about them.

For the Help Author

In this section, let’s look at some features that make it easier for you to do your job. These are features and enhancements that affect your ability to create quality help efficiently.

Advanced Style Sheet Enhancements

In Flare 12, the Advanced Style sheet editor gets a welcome overhaul. Now you can see multiple media sections in your style sheet–at the same time! I can’t tell you how many times I’ve made a change in the style sheet, then looked at my topic, only to find that my changes weren’t applied like I expected. When I looked back at the style sheet editor, I (eventually) discover that I was in the print media section, rather than the default section.

Flare 12 supports multiple media sections as columns in the advanced style sheet editor. You can pick which media types are visible, and as you scroll through one media section or expand a group in one media section, all media sections are synchronized, so you can quickly and easily see your settings across media types.

This feature alone is a good enough reason to upgrade to Flare 12, in my opinion.  (Click the image below to see a full-size version.)

In the image above you can see how I have three media sections open at the same time. Note that the font-family setting is different between the default medium and the print medium. Also note that in the third column, the font family option is grayed-out rather than in black like in the other two columns. This tells you that the setting is being inherited from another location; it has not been explicitly set for this media type. In this case, the font is being inherited from the default section for this element.

You’ll also note that the third column is a media query. That’s right – the Flare style sheet editor now recognizes and lets you work directly with device media queries! I’ve been doing this in the CSS code for a while now, so it is very nice to see this feature float up into the main Flare interface. You can define media queries in Flare, and you can view and edit those that have previously been defined. If you aren’t familiar with media queries, they are a feature of CSS 3 that allows the browser to deliver different CSS settings when certain conditions are met. In the screen shot above, the settings defined for this media query will show up when the user is on a screen, and the width of the browser window is smaller than 500 pixels. There is a lot on the web about media queries, so I won’t try to teach it all here. The key phrase to search on is ‘media queries.’

Also of note in the advanced style sheet editor is a new section in the bottom left that shows you any comments you’ve made for a style, as well as information about the property you have selected. It’s inline help for CSS in the editor, which is pretty nifty.

Finally, there is a cool new feature available in the advanced style sheet editor: you can link a style to a condition. When I first saw this feature, I wasn’t sure exactly how it would be helpful. Now that I’ve spent time working with it, I’m pretty excited about it. A lot of my clients have certain content that should only be viewed by help authors (notes to self, sources of information, etc.). They have other types of content that should only be viewed by people internal to their company (bug numbers or feature request numbers that were responsible for certain changes in the content, etc.). In the past, you’ve had to do two things to make this work. First, you have to apply a condition to this content so that it won’t get included in the wrong output types. Second, you’ve (optionally) had to apply a style to this content so it stands out when you are working on the content in Flare. Now, you can just apply the condition to style in the style sheet, so that whenever you use that style, the linked condition is invoked. If I have a paragraph style for “do not distribute” content with font in bright red, or something, I can apply the condition to the style, so that any time I use that style, that content always uses the associated condition.

If you are looking for that style setting, it is kind of hidden. Open a style in the advanced style sheet editor, view the All Properties option, and expand the “Unclassified” group. You’ll see a setting: mc-conditions, with a menu button to choose which conditions apply to this style.

Flare 12 also introduces support for style IDs. In the past, Flare’s editor would only work with style classes. Now throughout the system you can now either apply and work with classes and IDs, giving you more powerful control over your layout, and allowing you to use the semantically-correct constructs how they were designed in CSS and HTML.

Single Sourcing Enhancements

Flare 12 provides a lot of new features and enhancements related to content single sourcing that advanced users of Flare are going to absolutely love. If you’ve used snippet conditions in the past, Flare has new snippet condition superpowers. In the past, when you inserted a snippet into a topic, you would then open the topic properties, and specify which conditions would be applied to all snippets in that topic. Now, you can set snippet conditions separately for each snippet that is inserted into a document. That means, you could use the same snippet in two places in the same topic, and get different information from the snippet, based on the conditions applied to the snippet each time it was inserted.

Snippets can also now be pinned, so you can keep track of your most-commonly used snippets and find them easily. In addition, the insert snippet window also shows you the most recently used snippets, making it easy to find recent snippets and insert them into a new location.

Another new feature tied to snippets includes the ability to set variable definitions for snippitized content when the snippet is inserted into the topic. So if you have a snippet that has installation location for Windows and Linux, you can insert the snippet once, and set the variable definition to be the Windows installation location, and you can insert the snippet a second time, and set the variable definition of the second snippet to be the Linux installation location.

In the past you’ve had to have separate glossary files if you wanted to only generate some glossary terms for a given output. Now you can actually apply conditions to glossary terms within the glossary editor, so you could conceivably have a single glossary file that generates many different outputs depending on the conditions applied to the target that uses the glossary file. Another enhancement in the glossary is the ability to add variables to either a glossary term, or a glossary definition, giving you more powerful single-sourcing capability with your variables.

Links and Cross References

When you are creating links to content, you’ve traditionally had to either link to a heading in a document, or go into the target in advance and create a bookmark that you can link to. In Flare 12, there are additional options when you create a link or cross reference to a topic in the help system. The link window now shows a variety of items you can link to, including individual paragraphs, ordered list items, unordered list items, drop-downs, expanding text, or even stylized items. When you select one of the items here, Flare opens the target topic and generates the bookmark automatically, saving you a step, and making the process of creating links or cross references much simpler and faster.

This new feature is available wherever the select bookmark window appears, including in the TOC, links, cross references, etc.

Flare 12 addresses an issue from previous releases related to cross references with variables. In previous releases, if you created a cross reference, and the target heading had a variable in it, the variable text was ignored and left out of the heading. So, for example, if the target heading had “Discover <Product Name>’s New Features” where “<Product Name>” was a variable, a cross reference to that heading would be generated as “Discover ‘s New Features”. That bug has been resolved, so cross references to content with variables now render with the variables as you would expect.

Responsive Layout Editor

If you want to create responsive layout in Flare’s editor, there is a new editing panel for working with responsive layouts. Flare will create the divs and help you style them so that content can move dynamically on the page, based on the viewport size. I anticipate that this will be widely used for creating home pages with TopNav output, but I don’t know how often the average user will be working with this panel. Creating responsive layouts doesn’t seem to me to be something that you are likely to do for individual help pages in your system, so this seems most useful for the main landing page in the product, but it is nice to see this functionality baked into Flare.

64-bit Support

Flare is now a 64-bit application. This means Flare will be better able to access the resources available to a 64-bit operating system and its programs (utilizing 4GB of RAM or more, for example). In theory, this should make Flare run faster even when you are asking it to do memory-intensive tasks. In practice, I have a pretty powerful machine and I don’t see any noticeable difference between versions 11 and 12, but I’ve seen reports from some users who say Flare 12 is significantly faster for them, so your mileage may vary here.

The move to 64-bit may cause some people heartburn, because MadCap is not publishing a 32-bit version, as far as I am aware. Comments in the MadCap forum suggest that people who want a 32-bit version are being asked to contact MadCap Support directly. It will be interesting to see if there is a 32-bit version, or if those using 32-bit operating systems will need to stick with Flare 11.

Update: (3/17/2016) It appears there is a 32-bit version, but you need to contact MadCap to get it. 

GIT Support for SSH

There are several new features in terms of source control, but the one I was most excited about was an SSH connection for GIT source control. Our GIT repository can only be accessed via SSH, so we couldn’t use the previous GIT integration with Flare. In the end, I still couldn’t get Flare 12 to authenticate with GIT (GIT was returning authentication errors), but our team already widely uses Smart GIT, so I didn’t pursue the issue.

Something new in Flare 12 for source control in general is that Flare now recognizes if a project is bound to source control when you open a project file. If Flare detects that a project is connected externally to source control, Flare will give you the option to automatically set up source control in Flare. This is nice if you want to automatically connect, but I suppose that if you DON’T want to connect the two, this dialog would get old quickly, and I haven’t seen a way to turn it off (yet).

XML Editor Enhancements

There are several enhancements to the XML editor. First, the XML editor now lets you choose any of your media types in the Media drop down list. This means you can easily switch your WYSIWYG editor to show you how the topic might be rendered in mobile, or tablet view, or even based on a media query, if you have one defined in your style sheet, which is pretty handy.

My other favorite enhancement to the XML editor is Flare has simplified the process of inserting drop-down text. Previously, you would write your content, and then you would select the entirety of the content that would be in the drop-down. Then you would click on the drop-down button, and Flare would verify that you wanted the first ‘paragraph’ to be the drop-down head, and the rest of the content as the drop-down body. Now Flare skips that last step. It automatically converts the first ‘paragraph’ into the drop-down header, and puts the rest of the content into the drop-down body. A minor change, but it saves a click and makes the process that much faster.

For the Help System Users

So lets take a few minutes and review some features that make our output even more awesome for our customers/users. 

Runtime Skins

Runtime skins allow you to change the skin that is being applied to the topic via a parameter you pass through the URL. Madcap’s main help example shows how users could switch their skin by clicking a button in the interface. While this is interesting, I don’t think it is as practical as the next example, which is allowing you to call, via URL a specific skin. So you can have a plain skin, that doesn’t have a header or menu or whatever, and you can link to that for field-level context-sensitive help. But main links open in the regular skin. This isn’t groundbreaking in terms of new functionality, but it does improve the experience for our customers.

Word Enhancements

If you generate Word output, check out the features list for Word from Flare 12. There are a host of new features including how Flare treats floated DIVS, rendering of transparent PNGs in Word, as well as the ability to take tracked changes from Flare and convert them into Tracked Changes in Word (which isn’t useful for your customer, but can potentially be very useful for reviewers.

Multilingual Output

I haven’t worked very often in multi-lingual projects, but for those of you who do, you will be very interested to see how Flare 12 improves your workflow. Flare will now render multiple languages for each of Flare’s output types. The language tab in the target lets you select multiple languages (via linked targets), and specify which order they are built in the target.

Smart Quotes per language

Many Americans may be surprised to learn that quotation marks vary by language. In the past, Flare has just inserted American-style quotes into your content. Flare 12 is smarter, and based on the topic’s language, Flare uses smart quotes that are applicable to the language. It is important to know that Flare doesn’t automatically fix existing quotes in a project. It takes new quotes and applies the smart quote feature as the quotation mark is inserted into the topic. If you want to update the quotes in your project, MadCap recommends that you use “Find and Replace in Files” to search for the existing quotes (either smart or straight) and replace them with smart quotes.

Conclusion

I’ve been using Flare 12 for about a month and a half, and I’ve been very pleased with this release. There are features in this release that make an immediate positive impact on our documentation team, and I can see how they are going to benefit many longtime (and new!) Flare users. If I were using Flare 10 or older, Flare 12 is an obvious upgrade. If you’re using Flare 11, you may wonder whether you should upgrade or not. If it were up to me, I’d upgrade from 11 for a couple of killer features: (1) advanced style sheet editor, and (2) single-sourcing enhancements. Flare 12 also corrected the annoying bug for variables in cross reference titles, which made our doc team lead shout for joy.

If you are interested in learning more about Flare 12, I encourage you to visit MadCap’s website where you can see the new features, as well as see some upcoming webinars on the new features that are included in Flare 12. In addition, I wrote a separate article on Flare 12 that will be appearing in the April 2016 Intercom magazine from the Society for Technical Communication.

What are your favorite features in Flare 12? Let us know in the comments!

—-

Edit: 3/17/2016 – Hat tip to Austin Wright for pointing out some typos that have now been corrected.

As many of you are probably already aware, I’ll be presenting again at this year’s MadWorld Conference in San Diego. Over the next few weeks I’ll be posting a preview of each of my sessions for the conference. This serves two purposes. First, if you are considering going to MadWorld, I highly recommend it, and I hope my session descriptions will encourage you to register. Second, if you are going, I hope my descriptions will help you know if the session will be useful for you.

I’ll discuss my sessions in the order they’re being presented at MadWorld, which means I start with “Top Five Content Reuse Features in MadCap Flare,” which I’m presenting on Monday (April 11) at 11:05am.

First, this session is for the brand new Flare user, who is still working on understanding basic functionality in MadCap Flare. I’m going to talk about the following features in Flare:

Variables. We’ll discuss what variables are (unformatted text that can change definition based on target), how to create them, and how to use them effectively in Flare.

Conditions. We’ll discuss how conditions work in Flare, where you apply the conditions (based on file type), how to create and edit conditions, and I’ll give you some best-practice advice for working with conditions. I’ll show you how to customize your Flare 11 editor to show specific conditions while editing a topic, and cover how you use conditions in your target files.

Snippets. In this section we’ll define snippets and explain what they are and how they can be used. We’ll discuss how you edit snippets, see where snippets are being used, and we’ll show you how to use snippets for boilerplate features like tables.

Snippet Conditions. I’ll introduce the class to an advanced use of snippets where you can use conditions in the snippets themselves, and then you can determine which conditions from the snippets are used at the topic level.

Flare 12 Enhancements (hopefully). I expect that before MadWorld, MadCap will continue their tradition of releasing the latest and greatest version of Flare. I assume it will be called Flare 12, based on past experience with Flare. In this section, we’ll talk about any enhancements to the above features that are released as part of the latest MadCap Flare version. (If a new version isn’t released before the conference, or if there isn’t anything new to talk about here, I’ll talk about using nested TOCs in a multi-author project.)

I’m excited about this presentation. I love helping new Flare users understand how they can apply some of the features that make MadCap Flare the best help authoring tool on the market (IMHO).

If you are on the fence about attending the conference, I recommend you check out the conference website and see all the great presentations that are being given at the conference.