Merged Webhelp projects the way to go?


we developing webhelp 2 of our web-based applications. 2 different authors working on projects, , projects have different completion dates. build tags applied each project's topics, account following scenarios:
1. users have product installed, , acccess product only.
2. users have product , product b components installed, , access product product b topics integrated.
3. users have product b installed, , access product b only.
after separate projects build, 1 merged other, , final output of merged controlled using build tags. test of this, created 2 sample systems, complete product-specific skin, build tags, etc., , merged product b product (a master file). result when open book product b, whole new webpage launched (a new page navigation , contents panes)--i thought topics continue visible in 1 project. also, see discussion forum there no way hide books unless add code source. there many books product b should hidden. approaching wrong? help.

what getting wrong using build tags instead of merged projects capabilities.

regenerate without using build tags. should have structure this:

parent
...mergedprojects
......child1
......child2
......child3

make couple of copies of that. if following method on site, child1 users need delete whole child2 folder 1 of copies. open , find have working copy child2 topics, no toc it, none of index entries etc.

so create whole merge. developers deliver parent, child1 (if using method) , such other children required particular installation. can deliver , apply wrong name folders don't want shown, or similar method.

on way opening, sounds linking startpage of target instead of pointing toc of parent xpj of project merged.

take @ merged webhelp topic on site.



More discussions in WebHelp


adobe

Comments

Popular posts from this blog

Thread: PKI Client 5.00 install (for eToken Pro)

ATmega2560-Arduino Pin Mapping

Crossfader Arduino Tutorial