Wednesday 18 June 2008 5:10:49 am
As a relative new user/developer of eZ Publish, I have found eZ has some very unique styles, or approach to implement a CMS. Even though, I think it meat easy for the users and developers alike, hence it is "eZ", after several weeks reading the docs, I have still left a fair amount questions unanswered. Here is just some I think it bugs me most; they are may not critical for me to build a eZ powered site, but I think it seems so important to get every concepts right before starting implement any eZ Publish sites: 1. what is packages folder under the root eZ Publish folder for? Since it seems like all the package are stored under var/storage/packages. 2. There are additional location for the design folder under certain extension (e.g. the web interface)! This I think if not at all, at least not pay much attention in the docs. An extension as complex as the web interface can include packages, design, modules, settings...; but when install extension, the design are not copied into the main design folder, but as a sub folder under the extension. And, the template override system can recognize the design folder under activated extensions. Why not keep all the design in one place, after all we can create sub folder for each design? 3. Another is also regarding the "un-centralized" configuration file. Since extension can have settings folder which also includes ini files. Will be a time that I need to modify multiple files in different places but I forget one. Will this result hard to find configuration "bug"? 4. I think for a normal person, the "var" folder should not effect some "critical" aspect of the site. This means, even I delete all the content under the var file, my site should still running, and if caches are not exists, just automatically rebuild them. However, this is hardly the case. Because the sitestyle package installed by web interface was linked to page layout template which use ini settings to find the site-color.css and class-color.css file! I don't know if this the best practice. I think this is because in the Admin->Setup->Package, we can install, uninstall, remove packages if keep the package under the var/storage folder. 5.You can't manually directly delete cache also. The var folder is too important I think. 6.Too few good docs and books on eZ Publish which can access by public for free. And I think maybe there need a book on "Learn how to programming eZ Publish Templage Language in eZ Publish". Don't get me wrong, the template language itself is not comlex at all! But, you need have a certain under standing of the eZ system and and object model to because fluid. What default/available variables in what template (the doc only mentioned the variables in page layout template) and so on.
Certified eZ Publish 4 developer looking for develop information & collaboration.
|