Data-Driven Content Management

Another advantage of this data-driven approach is more subtle, but equally powerful. Assume that the data is in a database and not a document: now we can use the power of the database to relate different copy elements to different packages in a more efficient and dynamic manner.

Let's look at the difference between a distribution statement and an ingredient list as to how they would flow. In the current workflow, every product typically has its own "copy deck" or list of copy associated with a package. The distribution statement, even if it is used on 1,000 packages, is contained in each and every copy deck (some companies might group a few products together in a copy deck, but the process is still inefficient).