Skip to main content
TiffMhart
Participating Frequently
April 1, 2016
Answered

Conditional Build Tags: What is the difference between TOC, Topic, and Content-level CBT? Best practices?

  • April 1, 2016
  • 1 reply
  • 692 views

Hi. I am new to RH and we are attempting to use CBTs to identify which user groups will have access to certain online help. I understand the purpose of applying CBTs at the Topic or Content-level, but when attempting to applying CBTs at the Topic level, I was also given the option to add it to the TOC.  Can someone explain why I would apply it at both levels the TOC and Topic level?  Are there any GOOD resources out there that explain CBTs better? Everything I find just says "apply the CBT" which is frustrating!

This topic has been closed for replies.
Correct answer Captiv8r

Hi there

When you apply a CBT, you most often do it in order to "leave out" information that doesn't apply to a certain build of the output. Your post seems to suggest you have this basic understanding. And at the Topic level, tagging words or images will cause them to be removed when you apply and later exclude a tag.

As you have said, a tag can also be applied to the topic itself. And if you do that, the entire topic is removed when you generate using the build expression that excludes it. If that topic is in the TOC, because it is excluded, it is also removed from the TOC and will not appear in the TOC when you generate.

And lastly, you also have the option of tagging individual TOC items. And, just like the other things, if a TOC book or page has been tagged, it is removed from the TOC at the time you generate your output.

For me, I tend to avoid tagging the TOC. I typically tag whatever the topic is that the TOC page links to. Because I know if the topic isn't there, the TOC node disappears. So tagging the TOC is overkill.

Does that help make better sense of it?

Cheers... Rick

1 reply

Captiv8r
Captiv8rCorrect answer
Legend
April 1, 2016

Hi there

When you apply a CBT, you most often do it in order to "leave out" information that doesn't apply to a certain build of the output. Your post seems to suggest you have this basic understanding. And at the Topic level, tagging words or images will cause them to be removed when you apply and later exclude a tag.

As you have said, a tag can also be applied to the topic itself. And if you do that, the entire topic is removed when you generate using the build expression that excludes it. If that topic is in the TOC, because it is excluded, it is also removed from the TOC and will not appear in the TOC when you generate.

And lastly, you also have the option of tagging individual TOC items. And, just like the other things, if a TOC book or page has been tagged, it is removed from the TOC at the time you generate your output.

For me, I tend to avoid tagging the TOC. I typically tag whatever the topic is that the TOC page links to. Because I know if the topic isn't there, the TOC node disappears. So tagging the TOC is overkill.

Does that help make better sense of it?

Cheers... Rick

TiffMhart
TiffMhartAuthor
Participating Frequently
April 1, 2016

Thanks, Rick, for your quick response. Since I am creating a ton of content, I didn't want to tag it incorrectly and have to go back through everything later. Your answer tells me that I don't need to tag to TOC but only at the topic or content levels.

One additional question, any thoughts on why someone would tag at the TOPIC level AND tag specific content within the topic as well?

Regards ~ Tiffany

Captiv8r
Legend
April 1, 2016

Hmmm, interesting question. And prior to RoboHelp 2015, my answer would have been different. This is because RoboHelp 2015 introduces a new feature that is related to the Responsive HTML 5 output only. It uses tagging to accomplish the feature.

Up until 2015, we only used CBT to mark things to be left behind. That meant that in your output, there was no hint that CBT was even in play. But now, that playing field slightly changed. Using CBT now, you are able to tag content and Topics and the TOC and suchlike and have that tagging end up in the output. Then you can use this new process called "Filters", that enable the end user to click and choose to hide content they don't wish to see.

You can see this in action by opening one of the supplied sample projects (Travel the Whirls) and generating one of the Responsive outputs.

Click here if you need help with figuring out how to open one of the sample projects.

I'm hoping I provided some semblance of an answer you were hoping for.

Cheers... Rick