ibexa

Path

ez publish / technical manual / 3.10 / concepts and basics / content and design


Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.

Content and design

This section explains the fundamental concepts of content and design. It is important to understand what content and design actually are, how they interconnect and how the system handles these fundamental elements.

Content

In the world of eZ publish, content and design are separated. By content we mean information that is to be organized and stored using some structure. For example, it may be the actual contents of a news article (title, intro, body, images), the properties of a car (make, model, year, color) and so on. In other words, all custom information that is stored for the purpose of later retrieval is referred to as content.

Design

The information stored in a content structure must be presented somehow, preferably in a way that is easily understood by humans. While content means actual data, design is all about the way the data is marked up and visually presented. When talking about design, we're talking about the things that make up a web interface: HTML, style sheets, images that are not a part of the content, etc.

Templates

eZ publish uses templates as the fundamental unit of site design. For example, a template might dictate that a page should appear with the site's title bar on the top, and then main content in the middle. When the page is accessed, it then becomes the content management system's job to "flow" the content into the appropriate places in the template. An eZ publish template is basically a custom HTML file that describes how some particular type of content should be visualized. In addition to standard HTML syntax, it is possible to use eZ publish specific code to for example extract content from the system. The HTML syntax in the built-in/default templates follow the XHTML 1.0 Transitional specification.

The separation of content and design

While content is all about storing and structuring custom/raw data, the purpose of the design is to dictate how the content should be visualized. The result of a combination of these elements is a complete interface, as illustrated in the following diagram.

Content + Design = Web page

Content + Design = Web page

This distinction, and the system's ability to handle it is one of the key features of eZ publish. The separation of content and design opens up an entire range of possibilities that simply cannot be achieved otherwise. The following list outlines some of the most important benefits of this technique:

  • Content authors and designers can work separately without conflicts
  • Content can be published easily in multiple formats
  • Content can easily be transferred and re-purposed
  • Global redesigns/changes can be applied by simple modifications

Balazs Halasy (19/01/2005 2:33 pm)

Svitlana Shatokhina (31/03/2006 11:42 am)


Comments

  • Content format is required

    It's worth noting that though separation of content and design allows for the two to be processed and handled separatly and by different people, the format of the content - at least to some extent - needs to be decided upon before any design can be made. in other words, the designer needs to know what he/she has to work with. A good place to start is a XML Schema or document definition.