Best practices for documents with boilerplate
I apologize for the long post. This may be a how-to question as well as a best practices.
I have a project that includes several documents (more than the three in the illustration).

Each of the documents includes two different sets of boilerplate pages. They're boilerplate because they are identical. They go into each document at different places, but they are not simple block information. These boilerplate pages include images, several heads, and footers. Currently, especially the footers. By using boilerplate, I can maintain the pages in a single place so that they all read the same, but only until it's time to create the first Alpha draft. Then, I have to provide each book with its own copy of the boilerplate.

Because... The footers of each document include the product name. If they didn't, I'd just maintain the boilerplate in its own directory and insert the boilerplate doc using the book file where necessary. This is in fact what I do... but because of that changing footer, I have had to duplicate the boilerplate file for each book -- which multiplies the problem of maintaining all those "little changes" that crop up over time as the products mature and the docs go together. I use a text variable to maintain the name of the document... but even so, each book needs its own version of the boilerplate docs with the text variable set correctly in each component file of the book.
I'm looking for a way to maintain the boilerplate -- text&images or whole pages -- in one place and, when I cite them in the book file, they automatically adopt the correct product name for the book (presumably from the immediately preceding file) without me having to a) have a separate version for each product doc and b) adjust the content of a text variable.
Ideally -- I think -- this is the role of an INCLUDE command, where I could have a text-and-image object stored in a library somewhere and "insert it" into a regular page where I want the boilerplate to go (thus obviating the need to modify footers), but I don't believe ID offers that. And really, ID is WYSIWYG, so putting an INCLUDE in the middle of the text is probably not something that's going to happen. (However, I imagine it as something like linking to an external image. After all, the image appears, why not formatted text?)
Some kind of saved library object might work...
Have others run into this kind of issue? Is there an good way to resolve it? I'm coming up on another iteration of all these manuals, and I really would prefer not to try to maintain a version of the boilerplate for each product just so each product can have the product name in the footer (even if that product name is a text variable and I only have to change it in one place).
Thanks as always to the community.
-j
