eZ Documentation Center

This is outdated documentation made for eZ Publish Platform 5.2. It is being moved into the eZ Publish 5.x documentation, so please go there for most up-to-date documentation.

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3


eZ Publish is an Enterprise Open-Source Content Management System/Framework (CMS/F) at its core. It is highly extendable so with extensions it provides provides a Content Repository, Content Management and Web Content Management ("WCMS") capabilities and is highly extendable. Its default commercial Enterprise offering as of version 5.2, "is named eZ Publish Platform", is extended to provide full set of , it comes with Support and Maintenance as well as a set of features and services offering an Enterprise-grade solution. It also offers the access to additional services provided through the Cloud covering the domain of Customer Experience Management (CXM) capabilities.

What is eZ Publish 5?

Version 5 represents a big step forward for eZ Publish, as it introduces a whole new architecture and embraces the full Symfony2 stack and community around it. As is often the case with architecture, most of it is under the hood in current releases, and there is no new User Interfaces (UI) yet running on the new kernel; however with our "Dual-kernel" approach all existing UI's are still here running on legacy kernel. 

From high level 5.x kernel is:

  • “Ready Ready for the future, data compatible with the past”past: Content  Content Repository accessible via Public API & REST API v2  (full read & write support)
  • Full Symfony2 access”: Symfony2 Full-stack as the framework, extended with eZ Publish features 
  • DemoBundle front-end on top of eZ's Symfony2 stack (read only)
  • “Dual Dual kernel: Full code and data backwards compatibility”compatibility: 5.x stack is not fully functional on its own, it's combined with 4.x ("legacy stack") in a "Dual-kernel" setup (see developer section for more) to be able to provide all features you would expect; this is fully exposed to website developers as well that want/need to take advantage of legacy stack, 5.x stack or both.