MadCap Software Forums

Any updates on this?

We're preparing to open source some of our code, and while our general product docs are currently in Flare, it seems like the wrong tool for the open source doc content. We've started down the path with Sphinx, but also considering Jekyll or Hugo. Is anyone maintaining content ...

Bless you, marcinse. I never noticed that Paste icon! So much time to be saved going forward.

I actually just style the <pre> tag with class="code", and that seems to work without adding the enclosing div. Any advantage to one over the other? But also good to remember that "Group" function, which I ...

I do what you do, DTWT. Would love a better solution.

And for the record, I use <pre> tags, and it doesn't make a difference. The TextEditor is one of the low points of the Flare UI. It has several other flaws that wear me to the bone.

Just coming back here to confirm that adding the following line (right after the <MadCap:topicToolbarProxy />, though it could really go anywhere since it's invisible) to my master page did the trick:


<!-- Force inclusion of the DocNavigation topic in the output since it's not linked
from ...

Thanks, Dan.

The worst part for me was editing each menu level because I find that part of their skin editor to be tedious and confusing.

Yes, I recall having issues with that myself, though once you get it set, it's not something you need to keep messing with. Also, I believe the settings ...

I think I managed to figure this out for myself, though I'm still open to suggestions/corrections if anyone has alternate solutions.

First, it seemed evident that in order for any given Flare output file to "know" where the root folder is with respect to itself, without caring about the non-static ...

So now that Flare 2018 supports the side navigation accordion menu, is anyone who implemented this skinless solution going to switch back to Flare's native version? I wonder if it's worth the trouble, and whether it means another round of fiddling with the CSS to get everything working right.

And if it matters, I'm on Flare 2017 r3. Haven't worked up the nerve to upgrade to 2018; having performance issues as it is, and not sure that 2018 won't make them worse.

I would like to have a "Help" button in our toolbar that users can click on to bring up a general topic on how to navigate the documentation, but this is proving to be a vexing problem.

I've added a new button to the TopicToolBar skin, and I've set the button's Event->Click field to call a showHelp ...

Paul, did you mean in the Content Explorer rather than the Project Organizer? That was the case I encountered. I mistakenly conditioned out the topic file in the Content Explorer, so it got left out of the built output even though it was included in the TOC, and that topic was the one that was set ...

I had this same problem, albeit in a much later version of Flare (2017 r3) and for a different reason, but I thought it might be helpful to post here in case anyone else finds themselves scratching their heads over ways this can go wrong.

The first topic where the page number format was meant to ...

In thinking about this some more, I guess the reason this happens is that I've told Flare to push down the "importance" of those nested topics, so that they effectively become styled in the content at the same level as the subheadings in the "parent topic". In that case, it would be illogical for ...

Apologies if this has been addressed in another thread, but I couldn't find this exact issue.


My topics all start with H1 headings at the top, and work their way down as needed.
My TOC has nested topics, where the book topics are linked, so something like this:
Topic 1
Topic 1A
Topic 1B ...

Thanks, Alex. Sometimes you just need to talk yourself through it.

I just answered my own question through a bit of rubber duck debugging , but figured I'd post it here with the solution in case it's helpful to anyone else.

Question
I am generating a PDF target using the same TOC for both HTML5 and PDF output. The "front matter" pages are included in the TOC ...

Hi jcollins,

If I'm understanding you correctly, I think to get the context menu as a side accordion menu, all you need to do is swap out the TOC menu in this master page code:


<div class="grid-x">
<div class="show-for-medium medium-4 large-3 columns" id="nav-accordion">
<MadCap:menuProxy data ...

Big on commenting myself, but credit for those comments largely goes to Straygoat or you! : - )

And it turns out the slow behavior likely is more connected to our serving the pages from S3, so we need to revisit how we're doing that, but using visibility over display is still the right way to go.

Upon further fiddling after noticing that I could still see a quick flash of styling artifacts from the Menu skin, it turns out that the property you want to use to initially hide and then show the menu after it's been modified is 'visibility', as it allows the element to occupy space without being ...

Oh, I completely forgot that we set the display to 'none' on the #nav-accordion id so that it doesn't display until after the menu is modified by the script. Of course once I change it to 'block', my "This is where the accordion menu would go" paragraph appears, and the page load speed is very ...

Well that's interesting. If I comment out the menuProxy and add just a <p> element inside that div, it doesn't show up at all; the bodyProxy content just takes the entire 12 columns.


<div class="grid-x">
<div class="show-for-medium medium-4 large-3 columns" id="nav-accordion">
<!--<MadCap ...

Using a Foundation grid, specifically, grid-x. Here's the master page code.

<?xml version="1.0" encoding="utf-8"?>
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" MadCap:lastBlockDepth="10" MadCap:lastHeight="608" MadCap:lastWidth="1175">
<head>
<link href="../Foundation ...

Thanks, Dave. I'm not sure I'm following you, but I tried adding both width and min-width properties to the #nav-accordion id in my CSS, and I didn't notice any difference.

Part of the problem may also stem from the way we're serving the pages, at least in our test environment. They're in an S3 ...

@cwilkinson (trying to tag someone doesn't seem to work, or am I doing it wrong?), I just noticed your earlier post about the same two issues I was having - the lack of accordion menu toggle buttons, and the inability to display the linked topic on a book-level menu entry. My post prior to this one ...

For the record, 2017r3 is still using Foundation 6.2.3.

And regarding the book level menu entries being able to both display their associated topic and toggle the menu, I found that I needed to add the data-submenu-toggle attribute to the foundation-menu-off-canvas-initialization.js (yes, I ...

Thanks so much, Dave! That's exactly what I needed to understand. I've got more learning to do about Foundation, but you and Straygoat have given the foundation. ; - )