• Technical Overview
  • Overview
    • What is Jahia?
    • The closer View
    • Technical Requirements
    • Everything is Content, whatever the type or source
      • Integrator and Developer Customization
    • Integrated technologies
    • Architecture Overview
    • Modules
    • Jahia's Different Actors
  • Web Layers
    • Content Flows
    • Templates and Views
    • The Jahia Template Studio
      • Page templates
      • Content Templates
    • REST API
      • Actions
      • Example : native iPhone/iPad application
    • Mobile Rendering
    • Macros
    • Filters
  • Back-end Layer
    • Workflow
    • JBoss Drools and event listeners
    • File Repository
    • Searching and Indexing
      • Full text queries using search tag librairies
      • Query Languages
    • Enterprise Jahia Tool - Authentication and Authorization
    • Import / Export
    • Enterprise Jahia Tool - Distant Server Publications
    • Portlets
      • Portlets vs. Modules
  • Enterprise Jahia Tool - Optimizing deployment and performance
  • Additional Resources

Page templates

Page templates are the default template type, and are made available to editors when they create a new page. At that point the editor may specify the template he wishes to use that will define the layout of the page. Building structured templates targeted to the specific site vertical makes it a lot easier for site administrators to make sure that the sites have a coherent structure and look, and will also help make changes later on.

Page templates (and content templates) may also inherit from a parent template, so you may, for example, have a “base” template that has a very free structure, and then inherit from it to build templates that have more rigid structures.