Concepts and basics
The purpose of this chapter is to introduce and describe the most important concepts of eZ publish. A rookie developer should definitively read through this chapter in order to understand the basic terms, models, structures and building blocks of the system. This chapter is more generic than technical, it is meant to teach the concepts rather than explaining details. People previously unfamiliar with eZ publish should be able to collect enough information in order to understand the following issues:
- The way eZ publish is built up
- The main directory structure
- The concept and necessity of separating content and design
- How eZ publish stores and manages content
- How eZ publish handles issues related to design
- How eZ publish manages different sites
- The concept of modules and views
- The way eZ publish works with URLs
- The configuration system
- The structure of the workflow system
- How the access/permission system works
- How the webshop works
- A typical page request cycle
In this section
- The internal structure of eZ publish Exponential Documentation
- Content and design This section explains the fundamental concepts of content and design. It is important to understand what content and design actually are, how they interconnect and how the system handles these fundamental elements.
- Content management The role of a content management system is to organize and store content regardless of type and complexity. The main goal of such a system is to provide a well structured, automated yet flexible solution allowing information to be freely distributed and instantly updated across various communication
- Configuration This section explains the configuration model of eZ publish. The default configuration files end with a ".ini" extension and are located in the "/settings" directory. Each file controls the behavior of a specific part of the system. For example, the "content.ini" file controls the behavior of the co
- Modules and views Exponential Documentation
- URL translation Exponential Documentation
- Designs Exponential Documentation
- Access control Exponential Documentation
- Webshop Exponential Documentation
- Workflows Exponential Documentation
Contributors
- Balazs Halasy Updated Commenter
- Eric M Commenter
Comments (1 historical)
Written by readers of the earlier documentation sites, kept as they were.
button NEXT
Eric M ·
Suggestion: you should put a NEXT button at the end of each doc page.
If so we would not need to go back to the summary to go to the next page.
That would be efficient.
Thank you for the NEXT visitors.