Multiple Outputs Using the Build Module

[kwag_myers]

One of my project teams has Flare's Build Module which they use to generate an output themselves from source control. Now they want to have two versions of the output and are asking how to utilize the Conditional Tag feature in Flare since they have no UI? My plan was to tag the TOC entries, but the developers have no way of telling Flare to Include/Exclude the tagged topics.

[doc_guy]

I think you just need to create separate targets with the conditions applied to the targets. Then tell them your build team which target does what. You can then generate at the command line by target name. Or did I misunderstand?

[kwag_myers]

That's what I needed to know. Thx DG!!!

[ericjohnson7]

Just to reduce confusion... shouldn't this subject be discussed under a new topic titled "multi-channel publishing"?

This doesn't appear to be a single-sourcing subject. Correct?

[kwag_myers]

Just to reduce confusion... shouldn't this subject be discussed under a new topic titled "multi-channel publishing"?

This doesn't appear to be a single-sourcing subject. Correct?

My understanding of multi-channel publishing is multiple output types, e.g., ePub, WebHelp, and Mobile. What I'm working on is two versions of WebHelp from the same doc set with the omission of tagged topics in one version. Unless my understanding of the two is incorrect, I don't see how this falls under multi-channel publishing.

[NorthEast]

The forum is called "single-sourcing", which I always assumed means using a single source to produce multiple outputs (as it says in the forum description).

I don't think it matters what those outputs are, or whether or not they're the same 'channel'.

Myself, I'd also include re-using snippets within a single output as "single-sourcing".

[kwag_myers]

Thanks Dave! Just as a follow up, we ran into a few warning issues which caused the build to fail (mostly Accessibility). On the Warnings page of the Target Editor, I turned off the warnings listed in the Targetmc.log. Now I'm investigating the warnings to be sure it's alright to have them turned off.

[doc_guy]

In my most recent MadWorld presentation on Single Sourcing, I discussed this very issue. Single Sourcing, in my opinion is a term that includes multi-channel publishing.

Here is my opinion on how they are related:

[ericjohnson7]

Thanks Paul, nice Venn diagram!

Here's my 2 cents: I believe it will be beneficial for the forum and Flare documentation to start separating out single-sourcing from multi-channel publishing - only because it helps bring focus to user issues.

In my opinion, single-sourcing includes the elements Flare "pulls" from (e.g., snippets, topic files, variables and conditions, etc.). These are the "sources" or source controls.

Multi-channel publishing would be tools Flare uses to "push" (e.g., builds, targets, etc.). Even if the user is just using a single channel this would still be a part of multi-channel publishing.

It's true that there will always be some cross-over, but it may help users to focus on the specific Flare elements rather than grouping everything under one big tent.

Just ideas for future consideration...