5 Replies Latest reply on Apr 23, 2008 10:14 AM by Peter Grainge

    RoboHelp 7 - multiple projects

    TMSpats2 Level 1
      I am using the new Tech Comm suite - RH7. I was asked to do a little research on meging multiple projects. Since I have not done it before, I was hoping I could get the basics here.

      We have quite a few applications that will be available from a portal menu. There will be a RH project for each application. There will be a separate project for navigating and using the portal. We need to be able to publish according to what the client has purchased. Since a client will need to know how to navigate the portal, we would need Navigation for each client, but then we would pick and choose application documentation. Does that make sense?

      So one client might get Navigation and App 1; another might get Navigation and App 2 and App3...etc.

      Any direction would be appreciated.

      Thanks

        • 1. Re: RoboHelp 7 - multiple projects
          Peter Grainge Adobe Community Professional
          From the sound of it your merge relates to merged webhelp sitting on a server rather than merged CHMs sitting locally. If so, then there is a full article on my site explaining the procedure. Whilst the screens are from earlier versions of RH, the procedure is still unchanged in RH7.

          Essentially you will create a parent project which is just a shell. Then you create child projects as required. Any one customer gets the parent and just those child projects they require. For that reason you will need to be careful about creating cross project links so that you do not link to a topic that the client might not have. 404 errors are not pretty!

          • 2. Re: RoboHelp 7 - multiple projects
            jdcyclone1 Level 1
            Merging of projects is more useful in a situation where multiple team members are going to be collaborating on different pieces of the same project. Let's pretend the team is working on a help system about soda pop. One team member would work on the Pepsi help topic, and one would work on the Coke help topic. When both team members output to the same place, the TOC for that project is going to grab both the Pepsi and Coke topics and merge them together in the project's TOC.

            I think you would be better served just creating multiple (client specific) table of contents. That way if you need to output help for Company X, all you have to do is tell RoboHelp to use that company's specific TOC when generating their help.

            This is just my opinion, but I think this is the best route to follow.

            Hope it helps!
            • 3. Re: RoboHelp 7 - multiple projects
              Peter Grainge Adobe Community Professional
              If TMSpats2 has 10 products and customers can have any combination of them, that's a lot of tagging to include/exclude topics and a lot of generating the different outputs. Just because a topic is not in the TOC does not mean it is not in the output.

              With merged help, you generate each project once and just deliver the required combo.
              • 4. Re: RoboHelp 7 - multiple projects
                TMSpats2 Level 1
                Yes, you are correct. We are using conditional build tags a lot and the projects are getting very complex, but ....that is what product management wants.

                ...and soon we will be throwing in the multiple translations:)
                • 5. Re: RoboHelp 7 - multiple projects
                  Peter Grainge Adobe Community Professional
                  They want complex projects or they want the ability to just deliver what is wanted. Surely they say what they want, delivering it is your call.

                  My point here is that with merged help your tags could go out of the window and life would be simpler.