Hi all,
I've got an existing single-target WebHelp project, no condition tags in there yet. I need to add a small batch of content for a FAQ to the existing target, and the FAQ is also going to be used separately. So now I need to make my existing project a single-sourcing project.
I've added a FAQ-only target. Now, do I need to add condition tags only to the new content I create for the FAQ, or do I have to go back and add condition tags for all of the project's content? Content is included by default unless there is a condition tag to exclude it, correct? No way to have everything excluded by default unless condition-tagged to be included in a particular target?
Thanks!
Adding single-sourcing to a project - automatically exclude?
Re: Adding single-sourcing to a project - automatically exclude?
Depends on what type of target it is. If the FAQ is only going to be delivered as a PDF, then you could create a separate TOC that included only the FAQ topics and then associate that TOC with the new target. When you build that target, only the topics in that TOC will be included.
If the target is some type of online output, then yes, you'd need to exclude any topics that you don't want to be included in the FAQs output and vice versa if you don't want the FAQ topics to be included in your main online output. And yes, if you're building online output and you don't have something explicitly included or excluded, then it's included by default. You can apply condition tags to the folder level, which will make things easier -- put all the FAQ topics into one folder and apply the appropriate condition tag to that folder, then apply condition tags as appropriate to the content in other folders.
If the target is some type of online output, then yes, you'd need to exclude any topics that you don't want to be included in the FAQs output and vice versa if you don't want the FAQ topics to be included in your main online output. And yes, if you're building online output and you don't have something explicitly included or excluded, then it's included by default. You can apply condition tags to the folder level, which will make things easier -- put all the FAQ topics into one folder and apply the appropriate condition tag to that folder, then apply condition tags as appropriate to the content in other folders.
Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
-
stephgl
- Propeller Head
- Posts: 94
- Joined: Wed Jan 17, 2007 11:22 am
- Location: Greater Sacramento Area
Re: Adding single-sourcing to a project - automatically exclude?
Thanks so much (once again!) to you Lisa!
Both my targets are WebHelp, the main one being resident on the software user's computer. The small standalone FAQ will be added to our company website. So, it is GREAT news to my ears that I can apply condition tags at the folder level, this will take no time at all given how I'd organized the project. I was hoping not to run into a large hand-marking task (though I can sometimes use UltraEdit for making changes to large batches of files at once).
-Steph
Both my targets are WebHelp, the main one being resident on the software user's computer. The small standalone FAQ will be added to our company website. So, it is GREAT news to my ears that I can apply condition tags at the folder level, this will take no time at all given how I'd organized the project. I was hoping not to run into a large hand-marking task (though I can sometimes use UltraEdit for making changes to large batches of files at once).
-Steph
-stephgl