• 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

The Jahia Template Studio

As templates are not scripts, but defined inside the content repository, Jahia 6.5 introduced a new tool called the Template Studio to edit them. A template is actually a set of nodes that will define the layout of a page, allowing users with no scripting or HTML experience to easily edit or update existing templates. For advanced users with strong JCR skills, you could even export the template as XML, edit it and re-import it back into Jahia, should you wish to do so. Templates are regrouped in Template Sets, which can then be deployed to a site on the same Jahia installation or packaged as a module and exported as a WAR file to either be deployed on another development instance, or to another Jahia installation for staging or production.