MadCap Software Forums

It should be possible to hide this information using a real tag which is formatted by your stylesheet to not display, but so it can be extracted from the topic by software. For example, <div class="tooltip">...</div> with div.tooltip { display:none;} in the stylesheet.

Didn't find an attachment in this post, but some ideas:

• Leave the font size of the title unspecified, and apply the size as direct formatting to the title in each project to make the title fill the box.
• Don't specify the height of the box, and let it adjust to contain its contents.

You don't want to merge them, because that involves the TOCs and indexes and search all getting entangled. Each one sits in a separate folder on the server and you make a simple home page as another project with external links to the server URLs for the other projects.

Use a version control system to capture the state of the help at the completion of each version, and preferably use branches to allow you to modify the older help when needed.
Use a version-numbered folder on the server for each product version's help, as MadCap does, for instance, with the Flare ...

Create an additional empty alias file in your project and assign it to the target at the place you noted.

Something somewhere from the application has to indicate which help to show, and once you do that it shouldn't be hard to get it calling 3 different URLs, and you can set up your outputs with the full power of condition tagging in Flare.

You've turned show tags on, the button which is highlighted in orange at the top of the editor window in your screenshot. Click it again to turn that off.

HTML5 output is a set of files that make up a web site. You view it in a browser.

You have several options, but since you have a web app, you have fewer choices than you might have with a traditional desktop app.

First, the files need to be delivered somewhere. This could be within the user's web ...

I haven't used the MadCap Doc-to-Help (D2H), but I used D2H a long time ago and it looks like the same general product approach has been preserved through multiple owning companies and product versions since that time.

Doc-to-Help is primarily for manual writers who want a quick fix for generating ...

First off, you're going to have one target (of the appropriate type) for each output. 6 targets in this case.
There are several ways you can change what goes into each target.

To change the logo that appears above the help, you want to modify the skin. You'll just have to create different copies of ...

OK, so you had an inline style sheet. Flare reformatted it a little, but all looks OK until you get up to the line in the original which looked like:
.inner_table tbody > tr:last-child > td {

This is a valid CSS selector, but it can't appear raw in an HTML file because the > character is meaningful ...

When Flare adds images to the skin, the names are references to images it has embedded in another part of the skin file, not to files in your project. Changing the name in the code of the file does not cause it to grab a new image in this way. This skin is always self-contained in this way.
2018-09 ...

Choccie is on the right track. This looks very much like the topic has the wrong stylesheet attached or its stylesheet is missing. This could be because the original HTML files are linked to a stylesheet you haven't included in the project, or because settings in your project have forced a different ...

Add download="" to the link. This HTML attribute tells browsers to download the file rather than display it when the link is clicked.

The filename probably has some Unicode character in it which looks like a regular letter but isn't. Try renaming it and typing out the whole filename you expect it to have.

Try to reproduce this in a small project with just one or two topics and snippets. If you can, submit a defect to MadCap and attach the project. If you can't, it may give you more insight as to what is going on.

I think what you want to do is edit the autonumbering format for the first paragraph, and specify {n=1}. This resets the numbering to 1.
If your numbering is more involved, whatever you do normally when you want to reset the numbering, do it to the first paragraph in the snippet.

No idea. I gave them a test project demonstrating the issue. You should contact support about your questions.

Well, the thing is that the right-hand navigation pane is not really a pane in the same sense that the left one is. The right one contains per-topic different content and as such is part of the topic. You just need to format it in CSS to display so that it occupies space like a pane would. So, for ...

This is a bug in Flare 2018 which I have reported. It happens when you have a modular system of projects, and a context-sensitive help call goes into a topic in one of the subprojects whose contents has not been opened yet. That project's contents appears, but it goes under the attachment point for ...

So, Ardis, are these docs going to be the topics in your Flare project (each one of them an HTML page)? That's how the built-in Contents pane works; it displays a list of all the topics which are in the project's main TOC.

It sounds like you want the right TOC to be a list of the headings within a ...

There are several different ways that this whole architecture of app, help call, and context ID can be assembled. They are largely the same, but depending on the workflow in the specific software development tools, the exact steps may vary. In any case, something like one of the following happens ...

Other than "trial and error for as long as it takes" (which is a valid path, I happily admit), how do people learn the web of Skins, Stylesheets, Layouts, Targets, and more, that all have to be mastered to generate content with Flare?

You might want to read through the entire Get Started section ...

Flare does not auto-create index pages listing all the files in a folder like some web servers do. And if you are making HTML5 output, the topic files are not (normally) accessed directly, but through the skin file, so you can't even depend on the server hosting the help to do that.

What you should ...

in, mm, pt, etc. are physical lengths. (in is inches, and pt is points, which are 1/72 of an inch.) These are appropriate for a document that is expected to be printed (i.e. a print medium style sheet) or a format like a PDF that represents a printed document. You can also use them in on-screen ...