[ Home | TOC | Search | Post | Reply | Next | Previous | Up ]
From: tSQlTcSGoJ2
Date: 03 Oct 2015
Time: 06:36:20
Remote Name: 188.143.234.155
I have a variation for the step that asnigss a cover page via TOC —> Topic Properties —> Page Layout.First, create variables for document titles, version numbers, etc. (Handy for more than one reason.)Next, create a Target for a given manual, then in Target Editor —> Variables specify a given variable's definition in that Target. So, for example, the User Guide's local Target variable for the document title specifies User Guide, the Admin Guide's Target specifies Admin Guide, and so on. (Use a Batch Target to efficiently build multiple Targets…)The benefits are: A single cover page layout can be used across multiple members of a docs set's product family; one can use the Target's Conditional Text settings to customize what is included in or excluded from that Target's outputs; in PDF Options —> Document Properties one can customize the PDF tile (that appears in the PDF viewer's Title Bar), the document's keywords, etc.I hasten to add that I'm not dogmatic about using Targets. But they do provide an alternative workflow which in some contexts may offer advantages over separate cover files for a given member of a doc set's family…