We've got a StepNumber cross-reference type, but you aren't going to like how we got there.....
The install process of our app is very convoluted. In the install docs, we rely heavily on things like "skip step 3 if you use version X of app server Y." This isn't possible with ordered lists in HTML (and I don't think Flare supports it in any output types). Why is that? Because the number shown in the HTML is generated on the fly when the page is loaded, not when Flare writes the XML or HTML itself.
The HTML for an ordered list is:
Code: Select all
<ol>
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
</ol>
Which renders as:
1. Item 1
2. Item 2
3. Item 3
So the browser interprets the OL and generates a number; at build time, there isn't a step number that Flare can reference; it has no idea whether a step is the first or the fifth.
Instead of OL (which we would prefer to use), we're using Flare's AutoNumber feature. In the XML, it looks like:
Code: Select all
<p class="Numbered" MadCap:autonum="1.">After completing .....</p>
In the output HTML, it looks like:
Code: Select all
<td class="AutoNumber_p_Bullet" valign="top" data-mc-autonum="1.">After completing .....</td>
In the XML, the cross reference looks like:
Code: Select all
(<MadCap:xref class="Step_Number" href="#step_add_driver_to_classpath">stepĀ 1</MadCap:xref>)
The HTML for the cross reference looks like:
Code: Select all
(<a class="Step_Number MCXref xref xrefStep_Number selected" href="#step_add_driver_to_classpath">stepĀ 1</a>)
I don't think there is a solution for cross references pointing to the numbers of items in an OL.
One side effect of using the AutoNumber feature is that, under the covers, Flare builds all our procedures as tables, which has some unintended consequences. So this is definitely a kludge.
Thanks, and apolgies if this is tl;dr,
Kristen