General

  eZ Systems Website
  Technical documentation
  Editor documentation

This Documentation contains:
 
Technical documentation:



⚠ WARNING ! This documentation is deprecated !

Please go to the current Technical Documentation

Skip to end of metadata
Go to start of metadata

How your content is structured is a very important part of an eZ Platform project. Think of it as the database design of your application. We recommend that you read the Fundamental concepts documentation page, but you can also read the paragraph below for a short, straight-to-the-point introduction.

Content Model Overview

The eZ Platform content repository is centered around Content items, pieces of content: an article, a product review, a place...

Every Content item is built based on blueprints, called Content Types. They are named entities that define what information makes up a particular type of content: article, product review, place. An article could include a title, a main image, an abstract, the article's body, a publication date, and a list of authors. Those named entities are called Field Definitions, as they define what Fields a Content item is made of. A Field Definition sets the main information of a field: name, identifier, and type. Any Content Type can also be a container, meaning that it can act as a "directory", and contain other Content items.

The available Types for Field Definitions can be any of the installed Field Types, about 30 in the default distribution. Each is built to represent a specific type of content field: a text, a block of rich text, an image, a collection of relations to Content items, etc. You can find a complete list in the FieldTypes reference section. Every Field Type may have its own options, and comes with its own editing and viewing interfaces.

According to what you want to store, and what you want to do with it, you will create a set of Content Types and populate the Content Tree with them.

Create your Content Types

The site will use two Content Types: Ride and Point of interest

This is an overview of the content model we will implement an N-N relationship model:

   Ride ------------------------ Points of interest
           1..*                   1..*

Go to the admin interface ("/ez"), and authenticate with the default username: admin / publish. Click on Admin Panel in the Navigation hub, and choose Content types in the sub menu:

You will see a list of Content Type Groups. They are used to group content types in a logical way.

Click on Content and then click on Create a content type

We will create the Ride Content Type first:

Create the Ride Content Type

A bike ride, with a description and some extra info, like who took this ride for the first time, or points of interest it goes through.

Fill the form with this basic info: 

Name: Ride
Identifier: ride
Content name pattern: <name> 

Then create all fields with the following information: 

NameIdentifierField TypeRequiredSearchableTranslatableOthers
NamenameText lineyesyesyes 
ImageimageImagenoyesno 
DescriptiondescriptionRich textyesyesyes 
Difficulty levellevelSelectyesyesnoAdd a couple of levels, such as "beginner, intermediate, advanced"
Starting pointstarting_pointMap locationyesyesno 
Ending pointending_pointMap locationyesyesno 
LengthlengthIntegeryesyesno 
AuthorauthorAuthorsnoyesyes 

Populate your Content tree

Go back to the Content tree and create a Folder named All Rides using the Create button in the Action bar on the right of the screen.

In the folder, create a couple Rides.


 

 

 

 

Tutorial path