The automated output is formatted ('published' in H+M nomenclature) in the form of a web site, with Index.html serving as the TOC. In Chrome, it looks like this:
I brought the whole shebang into H+M, which did a passable job with automatic import, where the tree looks like this:
Clearly I have to do some work. The TOC in the H+M project is a non-linked list of the topics that H+M put under it, and the TOC of the auto-doc HTML site (index.html) has been auto-named "Base Library docs | Base Library Docs" -- plus, there is that suffix of "| Base Library docs" on names in the tree.
But the main questions are below:
Can this ever-changing (i.e. dynamic) auto-documentation be integrated into our overall H+M project?
If so, what's the best way?
- Links to the content on our server?
- Import into H+M, which is then integrated into the overall docs in the original H+M project (and how)?
- Is this a use of multiple TOCs?
- Probably not, since it is dynamic...
- but it would be VERY useful to have the integrated material automatically -- or easily -- updated just prior to publishing a new rev. of the overall docs.