But in the future I don't want to put all of my topics in a snippet to make them reusable
I like the breadcrumbs but generally putting topics in snippets makes no sense for my single source/topic based thinking ...
Have you other useful workarounds for this breadcrumb issue?
You´re right for online help output like HTML5 to use cross-references. But for my second PDF output I want to avoid many cross-references. So I put my topic to another TOC position instead.
But my really big problem is: I´m not sure if the snippet workaround is useful for multi user documentation projects in my team. I suppose/afraid we will put all of our topics (with snippets) in a whole snippet to reuse them for the feature. Hmmm, sounds a bit strange
You can have nested snippets, it's not a problem. For example, you may have a note that you want to include in lots of places, including in topics that you want to repeat in several places, so you'd have a snippet for the topic content, and in that snippet you'd have your note snippet.
Something else you might want to think of doing is using nested TOCs (I don't know if that's the correct term), particularly for your PDFs. I have a particularly large project, and each feature for the product has its own TOC. I then include each of those TOCs in the main product TOC. (If you're going to use those smaller TOCs in your Help target as well, then you may still need to do the snippetty thing to avoid breaking your breadcrumbs.)
Matze, take a look at this thread, where we decided on a different way to approach the same problem, without using snippets. This workaround uses bookmarks instead. Look to the bottom of the thread.
Dmuir wrote:Matze, take a look at this thread, where we decided on a different way to approach the same problem, without using snippets. This workaround uses bookmarks instead. Look to the bottom of the thread.
