Some remarks on how we used the eZ Publish multi-site capabilities in 4.x Donat Fritschy / http://www.cjw-network.com Basically, eZ 4.x allows to combine everything that makes up a independent site into an extension, namely: - Design - different design for different site accesses - override of templates via override.ini - override of templates by placing them at the corresponding place in the directory tree within the extension without the need for override.ini - Settings - global settings for this site in /extension/{site}/settings - override of settings in /extension/{site}/settings/override - individual settings per site access in /extension/{site}/settings/{site access} - (we also implemented site access groups in a kernel hack) - Host/URI Matching to site access - activation of other extensions specific to this site - but it it also possible to include own - Classes - Modules - Cronjobs - Commandline Tools - Libraries - ... - Separate VAR directory per site - Storage - Logs - Cache => and all this by activating the extension in a single place, the global site.ini