MadCap Software Forums

In procedural steps we write (using Word), we include a checkbox the left of the step number so clients can check each step they've completed. How can I accomplish this in Flare? From what I've seen, I can either use a bullet or a number; not both.

Easiest option would be to use a table. Put the checkboxes in the first column and the list items in the second column.

I just tried doing that and I think that will be the quickest way.

Thanks!
Russ

Alternatively, you could set up a paragraph style to do it automatically. I use something similar in one of my projects.

First create a new paragraph class, and set up an auto-number style for the numbering you want, e.g. '{n+}. '

To include a checkbox, put the image that you want to use in your project, and set it as the background for that style.

The following is an example of the style. The checkbox image used for the background is Content/Resources/Images/checkbox.gif.
Which looks like:
Depending on the icon size, you might need to experiment with the positioning and margin settings to get it looking the way you want.

One other thing worth mentioning is that the editor window (and sometimes the preview) seems to have trouble showing background images, so you'll only see them when you build the project.

I was going to suggest that, but I don't think Word will accept an image when it's specified in the stylesheet. I know if I specify a custom image for a bullet list that the image isn't included in the Word output, which requires having to open the output in Word and modify the bullet style in Word. I'm not sure how easy it would be to fix the image in the Word output when the image was specified as part of a paragraph tag.

However, if the checkbox is inserted as a regular image in a topic, then it goes through to Word. (Which is why I figured it would be the easiest method.)

If you're only designing online help, though, Russ, then I'd go with Dave's suggestion.

Dave, I really like that approach too. We'll have to play around with it and see which way will work best. Right now I don't know if we'll ever need to go back to Word with our output so the style approach may work.