This is a key concept in Content Template Catalog and allows for much reuse of components by mixing and matching them in different ways throughout the site. Reuse is not only good for reducing maintenance, but it also ensures common designs and better site usability.
Each of the component configuration authoring templates has a matching presentation template that renders a component. This component is an HTML component typically in the case of a Block, and a Menu, Rule, or Navigator for the other types. This component is rendered by a special JSP that renders the component in the appropriate context.
Selected header and footer components are rendered before and after the main component, and the whole thing is wrapped in a <div> tag that can be styled using a CSS class.
For Lists, Slideshows, and Carousels, a “result design component” is also selected. This allows the same queries to be reused throughout the site, but with different fields being displayed with different formatting.
The component configuration types in Content Template Catalog are just a starting point. This is a method for integrating functionality with your content and giving non-technical users control over the functionality. They also represent a design strategy that encourages designers to build in a reusable way that can be applied throughout your site.
The types in Content Template Catalog are purposely quite generic, but this also means they are not as simple as they could be. You can always choose to build more specific configuration types if you want to offer a simpler interface for authors.
The role of JSPs in presentation templatesParent topic: Key features of web sites built with Content Template Catalog
JSP files set up a context for the execution of the main component. Setting context includes setting paths, categories, and templates into the request, then executing the component in either a selected context or the current page context.
The role of the Context Override field
Setting a context override is the key to getting many of the components to select content appropriately throughout the site. Overrides also allow reuse of these components (for example, by avoiding the hardcoding of site areas into menus and rules).