The content structure

These documentation pages are no longer maintained. Please visit the new documentation site.

Unlike other content management systems, eZ publish does not make use of a predefined "one-size-fits-all" content model. Instead, it allows the site administrator to create his/her own content structure using a unique object oriented approach. This makes it easier to structure, store, retrieve and present custom data. Instead of desperately trying to fit data into some predefined, rigid structure, we simply create a structure that fits our data. However, is it unlikely that everybody needs to create a custom content structure. This is why eZ publish comes with a set of ready-to-use structures and datatypes. It is also possible to modify and extend the built in structures. In other words, eZ publish offers both ready-to-use and custom content structure. This is one of the features that make eZ publish an extremely flexible and successful system.

Comments

Contents

eZ publish basics

The internal structure of eZ publish
Content and design
Content management in eZ publish
    A note about object oriented technology
    The content structure
    Datatypes
    The content class
    The content object
    Relation between datatypes, classes a...
    Content object versioning
    Support for multiple languages
    Objects, nodes and the content node tree
    Locations
    Sections
Site management in eZ publish
eZ publish URLs
Summary


Created

02/10/2003
10:24:39 am
by Balazs Halasy

Last updated

02/10/2003
10:24:39 am
by Balazs Halasy

Authors

Balazs Halasy



This page is part of the eZ Publish documentation. The documentation is available under the GNU Free Documentation License. All contributions will be released under the terms of this license.