I've got an odd question but am hoping someone here may have run into a similar problem and come up with a creative solution.
We have a single Flare Help project, out of which we generate multiple HTML5 Help systems (which share some topics, and have many unique topics). At the moment when we publish our various systems, we have to distinguish between each by publishing to a different location on our server. This becomes time consuming and error prone (automation helps, but doesn't solve every problem).
What we'd like to explore is a way to drop all the built Help systems into a common location.
My guess is that there's no way around a collision of identically-named Flare generated support files (index, etc).
Has anyone attempted something similar and/or come up with a working alternative?
many thanks in advance for any insights!
paul
"cohabitating" help systems?
-
kwag_myers
- Propellus Maximus
- Posts: 810
- Joined: Wed Jul 25, 2012 11:36 am
- Location: Ann Arbor, MI
Re: "cohabitating" help systems?
So, basically what you need is a conditional tag for the output folder? I have the same issue when generating different output types, so I have folders setup in the project folder for PDF, WebHelp, etc. I just have to remember to change the Output Folder when I change the Output Type in the Target Editor.
"I'm tryin' to think, but nothin' happens!" - Curly Joe Howard