My work has upgraded our version of RoboHelp from 10 to 2015. Previously, we were using a workaround script to manage our single sourcing - however, because of layoffs, I don't actually know how this script works. Basically, it allows the "single-sourced" topic to appear in the webhelp of the project that's referencing the original, but not in the print documentation. So, we updated to RoboHelp 2015, so we could single source properly.
But, here's the issue. I started converting my first project, and pulled in all of the topics that I needed to reference. That all worked fine, except my broken links folder had about 20 broken links. I found that this was because a lot of the topics I was pulling in had links to other topics in the original projects. So, it seems those topics also needed to be pulled in. When all was said and done, I'd almost doubled the number of topics in that project. (Half now being shared from the resource manager.) Some topics even linked to topics that linked to other topics.
Are we doing this correctly? I started with a simple guide as a test and an example, but we have some projects that reference a lot more than this one did. Theoretically, if a topic links to a topic that links to a topic (and possibly ongoing to the nth time), then it seems like these projects could just keep getting bigger. Is there a better way to be doing this? Is there something that we're missing? It seems like there must be ...
Has anyone else worked with this? Any advice would be appreciated!!
Thanks!
