Quantcast
Channel: Adobe Community : Unanswered Discussions - RoboHelp
Viewing all articles
Browse latest Browse all 5136

Need to Split up a Project, but not Really

$
0
0

I have a project with about 150 topics that will soon grow rapidly for some of the following reasons. My project is basically a technical reference guide for a suite of software applications that Clients can implement all together as a comprehensive solution or individual components. Currently the project contains information for all the components divided into sections for each. Clients can easily navigate via TOC to the sections that cover the
information for the components they have implemented, but they usually just use the search to find what they are looking for. This has worked fine so far, but the problem is that the main (base component) is completely changing while the other components will remain the same (although they will continue to be upgraded with new enhancements). I would like to replace the old content on the main component with new content and just do away with the old, but that is a no go, because our organization will continue to support the current version of that main component for at least another five years. What makes it worse is that Clients can choose to keep using the older version of the main component, but continue on upgrading the other components. I do not want to split the whole thing in two, because more than 1/2 of the topics need to stay the same and be accessible from both the new and old versions of the main component topics. I do not want to maintain two instances of the same topics for the other components. In addition, I also want to be able to publish everything at the same time and to the same location. I also need to be able to keep the URL the same for Clients who continue to use the current version of the base component and have a different URL for Clients who are using the new version of that base component.

 

So basically, the whole mess looks something like this:

Robo_for_15-1.png

That all being said, does anyone have ideas as to the best way to accommodate this situation:

  • Conditional Tagging Only?
  • Conditional Tagging with two TOCs?
  • Make two Separate Projects and Publish to the Same Location?
  • Something Else?


RoboHelp 10 / WebHelp Pro (currently)


Viewing all articles
Browse latest Browse all 5136

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>