keronnet.blogg.se

1. #MADCAP FLARE WORD DOCUMENT HEADINGS HOW TO#
2. #MADCAP FLARE WORD DOCUMENT HEADINGS UPDATE#
3. #MADCAP FLARE WORD DOCUMENT HEADINGS SOFTWARE#

I can easily design all the nodes, and freely move things around until I’m satisfied with the structure.

#MADCAP FLARE WORD DOCUMENT HEADINGS SOFTWARE#

I actually use mind-mapping software (my fav is MindJet MindManager) to design the architecture of what will ultimately be a Flare project. I’ve actually used Word in a workflow to jump start an entire Flare project, but Word is only the intermediary.

Thanks very much for this post! I completely agree with using Word to jump start a Flare TOC or one or more Flare topics. But, if you like to outline your documentation before you fill in the content, it is definitely worth the time. There is a time cost to setting up a Word template and a Word import file in Flare to map to the Styles in the template. So why not just create the Word outline and import it into Flare? If you are only going to do it once, it may not be worth it. But it takes longer than creating a new Word document and adding headings to create an outline. Think about the experience of creating a Flare TOC with blank topics from scratch. But Word can also help create new content. When a Word shop switches to Flare, Word imports are central to the conversion process. The natural use for Word import is to import existing content.

#MADCAP FLARE WORD DOCUMENT HEADINGS UPDATE#

Add to that, the SME can update embedded objects and those will come over on the import also.īut Word can be used to as a starting point for a Flare project too. If you agree to only edit the Word document and not the resultant Flare topics, the SME can come back and make changes time and time again. One can place the Word file in a known place, such as on a network drive. An SME can create content in Word, including embedded objects, and that content can be imported into Word. If the SME is technically minded, there is a good chance she is familiar with Visio. It is almost certain the SME is familiar with Word. This is great if you want to manage content by subject matter experts. When a Word document with an embedded Visio diagram is imported into Flare, the resulting item in Flare is an image file and a reference to it in the corresponding Flare topic. But to someone editing the document, it can be edited as a Visio file. A Visio diagram embedded in Word can be seen by the reader of a Word document as a diagram. OLE enables embedding of other objects, such as Visio diagrams, into Office documents.

Microsoft Office supports a technology called Object Linking and Embedding (OLE). Word emphasizes headings in the default style galleries, which eases delineating Word headings into Flare topics. Styles in Word map nicely to CSS styles in Flare. If a Word document has been thoughtfully constructed with Styles, Flare can do a lot with it. It turns out that Word can be leveraged to improve one’s Flare workflow as well. In particular, two features of Word combined with Flare’s Word imports can be very powerful.įlare’s Word import functionality is strong. Word is everywhere and there are many solid use-cases for Word. But if you are reading this, you have probably passed through that learning curve. A desire to structure content, create a single source, and produce multi-channel output lead the author to ask, how can I do those things with Word? It’s a fair question and it isn’t impossible to accomplish those things with Word. And as author’s skills with Word grow, so does their attachment. When it comes to technical authoring, inevitably, someone will ask if they can use Microsoft Word.

#MADCAP FLARE WORD DOCUMENT HEADINGS HOW TO#

Here are a few thoughts about how to use Word as a part of your Flare infrastructure.