🚀 go-pugleaf

Steve,

Steve,

I see your point, but variables are what you really should be using
for the Title and Sub-Title in this case. When you add all of your
components to a book, just update the book with a control file that is
specific to that book only.

Another reason for not using cross-references in running
headers/footers is that if you convert your books to online PDFs,
these will be active links. Not much point in being able to jump to
the title page from every other page?

The issue of partial pages, if the text inset is to be part of a
single file, can not be handled using the book file approach. You have
to look at completely different model of publishing and maintaining
your documentation.

A lot of your methodology is really bordering on database publishing,
where the (book/document) component lists would be maintained in a
database and then dynamically assembled into FM docs using a tool such
as Miramo, Patternstream or plain SGML/XML. FM simply becomes a
publishing engine at this point and the generated book/document is not
meant to be maintained manually in FM.

In regards to the mentioned content management argument, Arbortext's
EPIC is simply another XML editor for content creation. You need a
collection of tools from Arbortext (E3, Epic Architect, Extend, etc.)
with a substantial price tag for a complete kit in order to do proper
content management and publishing. You also need the "Manage" module
to hook into systems such as Documentum, Filenet, InterWoven, etc.
(along with the repository software itself). It's nice to have deep
pockets ;-)