For example, you can create a 20 page booklet complete with cover file, 20 page content files, and a back cover file. When building your document in My Mimeo you choose all the characteristics of your book from cover, binding, paper, color, etc. During the process you upload three support files to provide unique content for this book. One for cover, one for content, and one for back cover. At any point using the Mimeo Connect REST API Proof Service you can pull new files dynamically from other locations and create new versions of your book document.You can apply the same concept to a single sheet flyer or poster. You would build your base document in your My Mimeo, then dynamically pull a PDF from any public location and merge with your flyer or poster document, creating an entirely new print document in real-time.Then with the Mimeo Connect REST API Order Service you can generate an order, set how fast you want your order, and the shipping options you want. It returns a quote that you can use to make ordering decisions from. Then your printed document arrives on your doorstep at your selected time.Its a pretty interesting approach to print-on-demand, self-publishing, web-to-print or what ever term you wish to use. It allows you to build base libraries of documents and dynamically generate print orders from these documents, using files uploaded by users of your web applications.I will be spending more time playing with the API over the coming weeks and providing more specific samples of how to build rich web and social applications that take advantage of the REST Print API.