Content conversion and generation is required by many interactive, web-based applications. Simplistic implementations of content converters, builders, and templates often cannot satisfy typical requirements such as high performance, end-user customizability, personalization, dynamic system updates, integration with multiple channels. We will present a pattern language resolving the main forces in this context.
A GENERIC CONTENT FORMAT can be used to represent content from any content source. PUBLISHER AND GATHERER are central instances to convert to and from the GENERIC CONTENT FORMAT, and to handle other central content management tasks such as cache lookup and storage. Conversions are performed by CONTENT
CONVERTERS. There are three alternative patterns to generate content on request: CONTENT FORMAT BUILDERS, FRAGMENTS, and CONTENT FORMAT TEMPLATES. A CONTENT CACHE is used to store and retrieve the content in a central repository.
You can access the paper here: Content Conversion and Generation on the Web.