Re: Linking Between and Among Merged Responsive HTML5 Projects:
I am outputting to Responsive HTML5.
I need to:
1) Create a Master Project and Child Projects, and;
2) Create links between Child Projects under a single Master, or;
3) Create links from Child Projects to topics that reside natively in a Master Project
I have to build an (effectively infinite) online resource manual for a government division.
I'm at the beginning of this, building the master architecture.
There will be a great number of child projects, but they will need to point to (link to) certain pieces of information that they have in common across the board, such as:
a) Screenshots of a computer system used by gov workers
b) Descriptions of various pieces of legislation, etc
c) Code tables that workers have to refer to
d) Other "appendix"-type things
e) Descriptions of various gov-issued mailings, etc.
f) Variables and snippets and modular, reusable content that must be globally used or applied across the entire Master Project
So it may be that some of the things in the list above -- if I cannot link from child to child in a merged responsive html5 environment -- would better be included in a Master Project itself...in other words, linking from Child Project to topics in Master Project...but it seems common wisdom advises that a Master Project should be an empty shell, i.e. just a table of contents containing child projects.
What I've seen in the forum so far regarding linking between and among merged projects refers to chm files, which so far as I know so far, does not pertain to merged responsive html5 projects.
My understanding of the concept and sequencing of merged responsive html5 so far is this:
1) Create Master Project, with Child Projects (placeholders) in TOC
2) Generate/Publish the Master Project
2) This will create empty folders (i.e. vessels) for the child projects
3) Child projects must be generated directly and individually (i.e. poured into) those vessels, one by one
(It seems to me so far, at least, that I therefore cannot really merge source files, but rather in effect only merge output/product files...)
This is where I get tripped up, because of course I want to link from source files to source files, not source to output/product files, and I want to keep my paths relative, because I will initially have to publish to a "development" intranet address for SME review etc, and only later when everything is finalized, publish again to a "final" intranet address -- though I will incrementally and iteratively be publishing more and more child projects into more and more vessels added to the master project.
In my researching of merged projects so far, I see references to chm files (which don't seem to pertain to merged responsive html5) and also to linking to "remote topics," which also don't seem to pertain to merged responsive html5.
Any help toward a macro understanding of this is appreciated. Is it even possible for me, using merged responsive html5, to link between and among child projects under a single master -- or from child projects to topics contained natively in a master?
Thanks very much,
p.s. sorry for the verbosity!