🚀 go-pugleaf

I have a refinement -- gathered by recent experience -- to add to my earlier comments.

I'm begining to perceive FrameMaker's conditional text feature as a way of turning on or off parts of a single content stream. One example would be controlling the presence or absence of print-only content threaded through single-sourced content intended for output as PDF (print) and On-line Help.

I'm still of the opinion that conditional text is *not* a good way to try and manage multiple content streams inside of a single container document. That's not say that it can't be done, particularly for two or perhaps even three content streams, but that trying to do so quickly reaches the point of diminishing returns unless one's content streams (or should I say feature sets?) are fairly static and not expected to grow.

I'm more than willing to learn otherwise: One of the things I like about tech writing is that I almost always learn something every day. It's just that when I reach the point of implementation I find that more-or-less parallel container documents that contain imported-by-reference text insets is a much saner way to manage multiple content streams than is conditional tagging.

Cheers & thanks to all again for their thoughts,
Riley