The content repository does not place any restrictions on the methods employed for delivering content via a public server infrastructure.
Applications are free to query the repository and process the data in any way desired.
Although there are no restrictions on publishing methodology, the repository API is intended to facilitate generic template-based publication, regardless of the specific presentation layer used. Following that is an execution step, during which setup tasks associated with the template are performed. Finally, the merging step combines the data and layout into a rendered page. The primary mechanism for matching URLs to Content Items are virtual URL handlers , .vuh files. An explanation of virtual URL handlers can be found in the tutorial on the Request Processor .