Hi Monique, This type of documentation screams for structured content, of course. This would allow you to easily solve the variables for product names, as well as combined conditions. Setting attributes on the book level, which are pulled into a <variable>. I have done this in many projects. Also, setting conditions via attributes and defining a build expression for filtering of the book content is something I have done with up to 50 different conditions, combining up to 40 of them in one single build expression.
Of course you need to have structured content for this. But then, working with unstructured FM content in the 21st century is really not done, if you ask me. Converting is fairly easy - we do it all the time - so if you do not have structured content yet, look in that direction for your best practices. Kind regards Jang _______________________________________________ This message is from the Framers mailing list Send messages to [email protected] Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to [email protected]
