• Templating and Integration Guide
  • Part 1: Concepts
    • The "Everything is Content" Paradigm
      • Content items are objects with properties that correspond to a type
      • Nodes are stored in workspaces, organized in trees
    • The rendering flow
      • To render a node, you need a view
      • To render a page, you need a template
    • Modules are packages used to deploy “code” into Jahia
    • The Jahia actors
      • Content flow
  • Part 2: Modules
    • What is a module?
    • Module type
    • Module creation
    • Anatomy of a module
    • Adding classes and Jars in modules
    • Spring files
  • Part 3: Templates and Studio
    • Introduction to templates
    • Studio
      • Studio overview
    • Creating a template-set
      • Using the Maven archetype
      • Using Eclipse
      • Using Jahia Studio
      • Update the Maven project when templates are modified in the Studio
    • Building templates
      • There are 3 different kind of templates
      • Main Resource and template resolution
      • Areas in detail
      • Content templates in details
      • Bound Components
    • CSS style sheets and design
      • Preparing your stylesheet
      • Including stylesheets in templates
      • Managing different stylesheets depending on the context
      • Print friendly CSS
      • CSS frameworks and handmade XHTML
    • Themes
      • How it works
    • Skins
      • Creating skins
      • Skin rendering
  • Part 4: Content Definitions and Views
    • Definitons
      • NodeType
      • Namespaces
      • Supertypes
      • Options
      • Node Type properties
      • Input masks
      • Default values
      • Initializers
      • Validators
      • Abstract types
      • In practice: create the node type definition for dogs
    • Views
      • NodeType folders
      • Output formats
      • Default view
      • Other views
      • Modules versus Components
      • Module packaging and deployement
    • Managing URLs in scripts
    • Managing lists
      • Summary for a simple list
      • Using list views
    • Managing and customizing navigation menus
      • Menu Rendering
      • Customization
  • Part 5: Advanced Techniques
    • Search and queries
      • Full text queries using search tag libraries
      • Queries
      • In practice: creating a custom search component
    • Forms
      • Principles
      • Form data parameters
      • In practice: Transform a custom HTML form into a Jahia valid form step by step
    • Macros
      • Macro implementation languages
      • Typical usage
    • Caches
  • Part 6: Setting up an integration environment
    • Software Requirements
    • Maven configuration for Eclipse IDE
    • Maven External Configuration
    • Creating a template set
  • Part 7: Step by step integration
    • Cutting of the mockup
    • Integration of the Base
    • CSS / Javascript integration
    • Creating the content zones
  • Further reading and resources

Studio overview

When switching to the Studio, your screen looks like the following.

Since Jahia 6.6, the studio displays and lets you manage all deployed modules of the Jahia plateform.

managing a module means to be able to handle dependencies between modules and be able to deploy it on a web project to make it available.

Toolbar

The Studio toolbar offers the following features

• New menu
  • New Template Set
  • New JahiApp
  • New My Space Module
  • Duplicate Template Set
  • New page
  • New content
• Deploy templates menu: displays the list of available web projects/web sites on the platform. If the current module is already deployed on a particular project/site its name will be followed by an asterisk character (*)
• Edit menu
• Export menu
  • Export war file: export the complete template-set in a war file, including the XML source but also script views, CSS and other resources defined at the template level.
  • Export: open a popup window with two links to download the source of the template set, in XML or in XML zipped format.
• Managers menu
  • Document Manager
  • Portlet Manager
  • Repository Explorer
• Cache menu
  • Flush cache for {selected element}: flush the cache fragment of the selected element in the workplan
  • Flush site caches: this entry does nothing in Studio Mode, works only in Edit Mode, as templates are not cached.
  • Flush all caches: flush all caches of the platform. Use with caution
• Administration: open the Administration back-office GUI
• Edit mode: open the Edit Mode (new window)
• User menu: display the current user account you’re logged in with
  • My Space: open your /jahia/start/ page
  • Logout: close de session

Template Selector

The first selector is the template Type

The second selector is the module name

It allows you to switch between modules.

Selector

The selector looks the same in Edit Mode and Studio at first sight but there are subtle yet important differences:

Templates tab: displays the current templates (whatever their type) as a tree.

Create Content tab: displays all the modules and their usable content types. If you want to use a module in your template, you have to create a dependency by enabling the checkbox near the module name.

Content tab: displays the content items other than binaries directly stored at the template level.

Files, Images, Themes tab: display binaries items directly stored at the template level.

Portlets tab: displays the portlets deployed in the template set.

Pages tab: displays pre-packaged pages that are part of the template-set and will be created (duplicated) in sites that use the template-set

Search tab: displays a search form. Works the same way as in Edit Mode.

Workplan

The workplan works exactly the same as the workplan in Edit Mode, using drag and drop, mouse selection and contextual right-click menus.

Unfortunately, templates are far less explicit than final pages, as there is no content in them most of the time, no data to format and very few things on which to apply style sheets. Remember that templates mainly define positions and are used to configure places where users will be able to enter content, so it’s a highly conceptual representation you have to get used to. The pages will really have their final look and feel once the users will put data into them, depending on the content types or features they insert.