Content Templates
As explained in the content flow diagram, content templates are used when an URL is requesting a content object that is not a page type, but any other. It is therefore possible to “decorate” a content type by adding navigation, headers, footers, or any other desired page elements around a rendered content object by defining a template and associating it with a list of types (through the Jahia Template Studio UI) for which it should be used. This is very useful for master/detail views, where the master list of objects would be displayed on a page, and the detail view could be a single content object rendered using a content template.
For example, let’s say you have news articles in your definitions, and you would like to display a single news article on a HTML page. You could have a home page that would list the abstract of the last ten news articles, and each of them would have a link to a single news article detail view, with all the details and sub objects attached to it. The home page would be rendered using the page template and the news article detail would be rendered using a content template associated with the news article type.

