• 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

Everything is Content, whatever the type or source

Another way of presenting Jahia is what we call “everything is content”. Since the very beginning, Jahia has been aggregating all kinds of content on pages, including dynamic content such as portlets. Jahia has always been able to mix applications and content on the same web pages. Jahia 6.5/6.6 takes this notion even further by easily allow the building of “content-based applications”, also known as “composite applications” that make it easy to build powerful applications that share a content store as a back-end.

In other words, working with Jahia means manipulating content and defining views as well as rules to be executed when an event is triggered on the content. Any content element stored in Jahia (text, image, PDF documents, portlet references, OpenSocial or Google gadgets) is considered content and therefore shares:

• Common properties (name, UUID, metadata, etc.)

• Common services (editing UI, permissions, versions, etc.)

• Common rendering and handling systems

Content is stored in a hierarchical structure (using Java Content Repository aka JCR standard), but as you will see it is possible to query or operate on it in other ways.