Skip to end of metadata
Go to start of metadata


Entries in italics are legacy terms (terms used in earlier versions of eZ) included here for reference reasons.



Access control

The mechanism of granting and prohibiting access to different parts of the website; see Policy, Role, Access function, User, User group.

More information (User Guide): Managing permissions.

More information (Technical Manual): Permissions.

Access function

The smallest element of the permissions system: a single component of a policy.

Action bar

A menu in the right pane of the Content mode. It allows you to create, modify and manipulate Content.


Legacy term for Field Type.




The basic segment of a Landing Page. Blocks can be placed on a Landing Page using drag-and-drop and later customized.

More information (User Guide): Adding blocks to Landing Page.


A directory containing a set of files (PHP files, stylesheets, JavaScripts, images, etc.) that implement a single feature (for example a blog or a forum). This is a term used in Symfony, which distributes both its main framework and extensions or addins in the form of bundles.

More information (Technical Manual): Bundles reference.




Contributor Licensing Agreement. An agreement which needs to be signed before contributing to the development of eZ.


Content Management System. This is the basic type of software that eZ offers.


Customer Experience Management. The whole of marketing and business activities, processes and tools connected with interaction between a company and its customers.

Cloud Services

A commercial component of eZ with options for gathering and using content intelligence, including capabilities such as recommendations or marketing automation.

Cloud Services is also available as a standalone solution.


The way of setting up an installation to have several web servers running eZ.

More information (Technical Manual): Clustering.


The Community Gateway for eZ users. Also, the open-source version of the previous generation of eZ products.


A library of independent components for Web applications. In the current versions of eZ replaced by Twig templates and Symfony bundles.


A PHP packaging system to manage dependencies. It is used in the installation and update mechanism of eZ. See

More information (Technical Manual): Using Composer.

Content items

1. In the broad sense, content items is everything that is placed on a site for the visitor to see.

2. (sing. a Content item, Pl. Content items) In the narrow sense, a Content item is a single object used on a site. It can be, for example, an article, a photo gallery or a blog post. Technically, a Content item is an instance of a Content Type (that is, it is a single object created on the basis of a "blueprint" which is the Content Type).

Occasionally, the term "regular Content" is used to refer to any type of Content other than a Landing Page.

More information (User Guide): Fundamental concepts.

Content Class

Legacy term for Content Type.

Content mode

The editing mode used in eZ Platform. The Content mode concentrates on creating, editing and managing Content items.

More information (User Guide): Content mode interface.

Content state

The status of a Content item version. Each version can have the status of Draft (created but not published yet), Published or Archived (removed or replaced by a newer version).

See also Content versioning.

Content tree

The structure into which Content is organized in the system.

Content Type

A template or blueprint for Content. It defines Fields and their Field Types which are then assigned Field Values when a Content item is created based on this Content Type.

Content Type is conceptually similar to a class in object-oriented programming.

More information (User Guide): Content Types.

Content versioning

A control mechanism for changes made to content. Whenever a piece of Content is modified, its previous version is preserved with an Archived state. You can view an earlier version of Content and revert to it if you decide to undo the changes.

See also Content state.


Cascading Style Sheets used to create and apply styles to websites. Can be used in conjunction with Twig.



Data Type

Legacy term for Field Type.

Demo Bundle

A bundle containing a demonstration version of a website created using eZ. You can use it to familiarize yourself with the system, or to create your own website on its basis.

There is a separate Demo Bundle for eZ Platform and eZ Studio.

More information (User Guide): Demo Bundle.

Discovery bar

A menu in the left pane of the Content mode. It allows you to navigate the repository.

Dynamic page

One of the types of Landing Page: a page with dynamically generated content.




Legacy term for Bundle.

eZ Enterprise

The current commercial stack of eZ. It contains the open-source eZ Platform component as well as eZ Studio.

eZ Platform

Open-source component of eZ.

eZ Publish Community

Open-source version of the previous edition of eZ.

eZ Publish Enterprise

Commercial version of the previous edition of eZ.

eZ Studio

Commercial component of eZ, together with eZ Platform it constitutes eZ Enterprise.




The smallest unit for storing data in the content structure. A Content item can contain multiple Fields, each of them with a Field Value. The Field Value must correspond to the Field Type as defined in the Content Type.

Field Type

The type of data which can be stored in a Field. Field Types which make up Content are defined in the Content Type.

Field Type is conceptually similar to a data type in programming. However, the available Field Types include both simple data types (for example integer or float numbers) and more complex structures (for example image, media file or binary file).

More information (User Guide): Field Types.

Field Value

The value which is assigned to a Field when Content is created based on a Content Type. The type of value is defined by the Field Type.

Flex workflow

A functionality for managing the Content review process. It allows you to ask other users to review your content and send the reviewers mail notifications.

More information (User Guide): Content review workflow.



Landing Page

In online marketing, the part of the website that a customer is directed to first when reaching a webpage through a search engine or a marketing link.

In eZ terms, a special form of Content. It allows you to organize the page using specially tailored blocks of content.

Landing Pages can be created in Page mode.

More information (User Guide): Creating content - Landing Page.

More information (Technical Manual): The LandingPage Field Type.


The way in which a Landing Page is divided into zones. Each zone can contain a number of blocks. See also Dynamic page.


General term for previous versions of eZ, from 3.x to 5.x.


The place in which Content is located in the content structure, indicated by a Location ID. A Content item can be assigned to more than one Location (have more than one Location ID), but a single Location ID can have only one Content item in it.

More information (User Guide): Content Locations.



Marketing Automation

A part of Cloud Services offering marketing automation capabilities: functionalities for generating and managing leads and sales management.

Media library

The place where all media (for example images, videos, etc.) are stored in the content structure. When choosing a piece of media to place in your content, you will use the Universal Discovery Widget.

Multisite setup

A configuration where one eZ installation serves multiple websites (for example, different versions of a company website for different international markets).




Legacy term for Location.



Object-oriented content structure

The fundamental idea behind structuring content in eZ. Based on the concepts of object-oriented programming, this structure treats every Content item as an object, an instance of a predefined Content Type, with a number of Fields reflecting its properties.

See Content, Content Type, Field, Field Type.

More information (User Guide): Fundamental concepts.



Page mode

The editing mode available in eZ Studio. Allows you to plan, create and modify content live, while previewing the effects of the changes in real time.

More information (User Guide): Page mode interface.

Performance mode

The editing mode available in Cloud Services.


See Policies, Roles.


The basic element of the permissions system: a rule defining access to one functionality of one module (for example modifying articles), with possible further limitations. Can be assigned to users and user groups.

Public API

A PHP API which exposes a Repository, allowing you to create, read, update, manage and delete all objects available in eZ, both Content and related objects such as Sections, Locations, Content Types etc.

More information (Technical Manual): PHP API Tutorials.




A part of Cloud Services containing an engine for gathering customer information and presenting recommendations. Powered by YOOCHOOSE!.


Storage place for all content in an eZ installation. It can be interacted with using the public API.

Can also refer to a GitHub repository (eZ uses GitHub to store and share its open-source code).


An API which allows you to interact with an eZ installation using the HTTP protocol, following a REST interaction model.


An element of the permissions system: a collection of Policies assigned to a particular user function (for example a sports section editor). Can be assigned to Users and User groups.




A demarcated part of the Content tree. Sections can be used to control permissions granted to users (for example, a "Sports Editors" group can be assigned Roles which only grant access to the "Sports" Section of website).

More information (User Guide): Managing Sections.

Service life

Support and maintenance cycle of different versions of eZ. See for detailed information.


A collection of configuration settings provided when accessing a website. A single site can have multiple siteaccesses which define the content and design of the page that will be displayed. This functionality can be used for example to create separate versions of the website for visitors and for administrators.

More information (Technical Manual): Siteaccess.

Smart Analytics

A part of Cloud Services containing an engine for tracking and analyzing visitor behavior on the website.


An open-source technology used for caching. See

More information (Technical Manual): Persistence cache, Persistence cache configuration.

Studio Toolbar

An action toolbar at the top of the screen in eZ Studio which allows you to create, edit and view content.

More information (User Guide): Page mode interface.


A PHP framework for web applications and a set of reusable PHP components. eZ has been using Symfony as its framework since eZ Publish 5.0. See




An instrument for customizing the visual aspect of a website. A template is applied to the content and defines the layout, themes and other graphical features with which content will be displayed on the page. eZ uses Twig as its main template engine.

More information (Technical Manual): Templating, Content view.


A PHP template engine used as the main template engine in current versions of eZ. See for more information.



Universal Discovery Widget (UDW)

A tool for browsing, searching and selecting content in the Content tree and Media library.


An account in which information about a user is contained in the system.

Technically, a User is a Content item of a special Content Type.

More information (User Guide): Managing Users.

User group

A collection of users grouped together for efficiency reasons. You can assign policies and roles to User groups as well as individual Users.

Technically, a User group is a Content item of a special Content Type.




A markup language for encoding documents (short for Extensible Markup Language). One of the formats for storing configuration data in eZ, as well as an output form for REST API.




A data serialization language (short for YAML Ain't Markup Language). One of the formats for storing configuration data in eZ.




A basic part of a Landing Page layout. Zones are are deployed over a layout in a particular position and can in turn contain blocks.


  • No labels