Tuesday 08 June 2004 9:55:20 pm
Here are the ones that I can answer: A.1 - this can be done to some degree by augmenting the standard user class. It is not as functional out of the box as some purpose-built newsletter solutions, but we like it because it is integrated into the other site management functions (access to restricted sections, automated signup, customized content, etc). A.2 - this depends on what makes these sites different. Each section of the eZ publish install can have a different design, different access settings, and different content. (see http://ez.no/ez_publish/documentation/ez_publish_basics/content_management_in_ez_publish/sections) A.4 - The roles and user permissions are quite precise, especially with v3.4. You can have very fine control over who can access what. Your biggest challenge will be automating the policy so that users inherit the correct permissios as they are created (this is not a problem to do, but will require some thought and planning). A.6 - The WYSIWYG editor does not have a spell check. I consider it to be the main weakness of eZ. (answer to C.4) I find that WYSIWYG is a bit of an overstatement, as it does not truly represent what will be published when the user selects "Send for publishing". You can modify the admin templates to create new version that is simpler, but there are many templates, and a complete customization would be a big undertaking - negating many of the benefits of a CMS. However, I have had success simplifying the admin by only modifying a few templates (pagelayout templates) in my projects, but it really depends on what you need. In any case, it is very flexible. B.1 - private (or customized) information can be cached under whatever circumstances you would like. I am not sure how the user would benefit from cached information if each user gets a different display, but we using design keys the cache can be controlled by many functions. We use such control to cache the first time a navigation tree opens to a particular level, and then when the user goes to another page it changes the nav tree but not the header, footer, and background. Regardless, the first time any specific content loads it has to be dynamically generated. B.2 - I know that CSS, RSS, PDF, and XHTML are built in from the start. I have read about SOAP, XML, and others, but am not sure. B.5 - it should be possible to have multiple sites (servers) point to the same database for content. I have never done this, but it seems possible. Good luck with your project... Mark
http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions
|