Entries in italics are legacy terms (terms us= ed in earlier versions of eZ) included here for reference reasons.
The mechanism of granting and prohibiting access to different parts of t= he website; see Policy, Role, Access function= , User, User= group.
More information (User Guide): Managing permissions.
More information (Technical Manual): Permissions= .
The smallest element of the permissi= ons system: a single component of a policy= .
A menu in the right pane of the Conten= t 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 cus= tomized.
More information (User Guide): Adding blocks to Landing Page.=
A directory containing a set of files (PHP files, stylesheets, JavaScrip= ts, images, etc.) that implement a single feature (for example a blog or a = forum). This is a term used in Symfony, w= hich distributes both its main framework and extensions or addins in the fo= rm of bundles.
Contributor Licensing Agreement. An agreement which needs to be signed b= efore contributing to the development of eZ.
Content Management System. This is the basic type of software that eZ of= fers.
Customer Experience Management. The whole of marketing and business acti= vities, processes and tools connected with interaction between a company an= d its customers.
A commercial component of eZ with options for gathering and using conten= t 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 runnin= g eZ.
More information (Technical Manual): Clustering.
The Community Gateway for eZ users. Also, the open-source version of t= he previous generation of eZ p= roducts.
A library of independent components for Web applications. In the current= versions of eZ replaced by Twig templates a= nd Symfony = bundles.
A PHP packaging system to manage dependencies. It is used in the install= ation and update mechanism of eZ. See https://getcomposer.org/.=
More information (Technical Manual): Using Composer.
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 si= te. It can be, for example, an article, a photo gallery or a blog post. Tec= hnically, a Content item is an instance of a Content Type (that is, it is a single object created on the basis o= f 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.
Legacy term for Content Type.
The editing mode used in eZ Platform. The Content mode concentrates on c= reating, editing and managing Content items.
More information (User Guide): Content mode interface(old).
The status of a Content item version. Each version can have the status o= f Draft (created but not published yet), Published or Archived (removed or = replaced by a newer version).
See also Content versioning.=
The structure into which Content is organized in the system.
A template or blueprint for Content. I= t 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 progr= amming.
More information (User Guide): Content Types.
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 Conte= nt 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.
Legacy term for Field Type.
A bundle containing a demonstration version of a website created using e= Z. You can use it to familiarize yourself with the system, or to create you= r own website on its basis.
There is a separate Demo Bundle for eZ Platform and eZ Enterprise.
More information (User Guide): Dem= o Bundle.
A menu in the left pane of the Content= mode. It allows you to navigate the repository.
One of the types of Landing Page: = a page with dynamically generated content.
Legacy term for Bundle.
The current commercial stack of eZ. It contains the open-source eZ Platform component as well as Studio.
Open-source component of eZ.
Open-source version of the previous edition of eZ.
Commercial version of the previous edition of eZ.
The smallest unit for storing data in the content structure. A Content item can contain multiple Fields, each o= f them with a Field Value. The Field V= alue must correspond to the Field Type = as defined in the Content Type.
The type of data which can be stored in a Fi= eld. Field Types which make up Content a= re defined in the Content Type.
Field Type is conceptually similar to a data type in programming. Howeve= r, the available Field Types include both simple data types (for example in= teger or float numbers) and more complex structures (for example image, med= ia file or binary file).
More information (User Guide): Fie= ld Types.
The value which is assigned to a Field w= hen Content is created based on a Content Type. The type of value is defined b= y the Field Type.
A functionality for managing the Content review process. It allows you t= o ask other users to review your content and send the reviewers mail notifi= cations.
More information (User Guide): Content review workflow.
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 li= nk.
In eZ terms, a special form of Content= . It allows you to organize the page using specially tailored blocks of con= tent.
Landing Pages can be created in Page mode= .
More information (User Guide): Creating content - Landing Page.
More information (Technical Manual): Landing Page Field Type (Enterprise).
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.
A part of Cloud Services offerin= g marketing automation capabilities: functionalities for generating and man= aging leads and sales management.
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 c= ontent, you will use the Uni= versal Discovery Widget.
A configuration where one eZ installation serves multiple websites (for = example, different versions of a company website for different internationa= l markets).
Legacy term for Location.
The fundamental idea behind structuring content in eZ. Based on the conc= epts of object-oriented programming, this structure treats every Content it= em as an object, an instance of a predefined Content Type, with a number of Fields <= /a>reflecting its properties.
See Content, Content Type, Field, Field Type.
More information (User Guide): Fundamental concepts.
The editing mode available in eZ Ente= rprise. Allows you to plan, create and modify content live, while previ= ewing the effects of the changes in real time.
More information (User Guide): Page mode interface.
The editing mode available in Cloud = Services.
The basic element of the permissions system: a rule defining access to o= ne functionality of one module (for example modifying articles), with possi= ble further limitations. Can be assigned to users and user groups.
A PHP API which exposes a Repository, allowing you to create, read,= update, manage and delete all objects available in eZ, both Content and re= lated objects such as Sections, Locations, Content Types etc.
More information (Technical Manual): Public API Guide.
A part of Cloud Services contain= ing an engine for gathering customer information and presenting recommendat= ions. Powered by YOOCHOOSE!.
Storage place for all content in an eZ installation. It can be interacte= d 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 HT= TP protocol, following a REST in= teraction 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 Us= ers and User groups.
A demarcated part of the Content tree<= /a>. Sections can be used to control permissions granted to users (for exam= ple, a "Sports Editors" group can be assigned Roles which only grant access= to the "Sports" Section of website).
More information (User Guide): Managing Sections.
Support and maintenance cycle of different versions of eZ. See https://support.ez.no/Public/Service-Life for detailed in= formation.
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.
A part of Cloud Services contain= ing an engine for tracking and analyzing visitor behavior on the website.
An open-source technology used for caching. See http:/= /www.stashphp.com/index.html.
More information (Technical Manual): Persistence cache, Persistence cache confi= guration.
Commercial component of eZ, together with eZ Platform it constitutes eZ Ent= erprise.
An action toolbar at the top of the screen in 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 component= s. eZ has been using Symfony as its framework since eZ Publish 5.0. See http= s://symfony.com/.
An instrument for customizing the visual aspect of a website. A template= is applied to the content and defines the layout, themes and other graphic= al features with which content will be displayed on the page. eZ uses Twig as its main template engine.
More information (Technical Manual): Design, Content Ren= dering.
A PHP template engine used as the mai= n template engine in current versions of eZ. See http://twig.sensiola= bs.org/ for more information.
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.
A collection of users grouped together for efficiency reasons. You can a= ssign 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 La= nguage). One of the formats for storing configuration data in eZ, as well a= s an output form for REST API.
A data serialization language (short for YAML Ain't Markup Language). On= e 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.