Manuel d'utilisation eZ Publish |
|
eZ publish est un CMS avec des fonctions prédéfinies permettant la gestion simplifiée de contenus, les workflows, la gestion des versions, le multilinguisme, le travail collaboratif ainsi que l'e-commerce.
Destiné aux entreprises, eZ publish offre une alternative aux ECMS propriétaires. Son modèle Open Source, respectant et intégrant les plus grands standards du Web, offre des facultés d'interopérabilité avec les services métiers de l'entreprise.
eZ publish est aussi un framework Orienté Object framework avec son système de classes paramétrables et extensibles ainsi que ses interfaces vers l’import export XML, RSS, SOAP,LDAP, Webdav et OpenDocument.
Open Net Sàrl, le plus ancien des partenaires de eZ publish en Suisse, met à votre disposition des consultants certifiés avec une expérience inégalée sur eZ Publish. Actif dans la communauté, Open Net Sàrl est à l'origine de la solution de gestion documentaire eZ DMS et de l'intégration eZ Sale entre eZ publish et OpenERP.
Avec eZ Publish, vous bénéficiez également de la garantie donnée par un éditeur stable, Fondée en 1999, eZ Systems est au cœur d'une communauté professionnelle articulée autour du développement d'eZ Publish. EZ Systems assure la pérennité du logiciel en maîtrisant son évolution et son support.
The eZ publish content structure is based on ideas borrowed from the object oriented world of popular programming languages like Smalltalk, C++, JAVA, etc. Superficially, object-oriented means nothing more than looking at the world in terms of objects. In real life, people are surrounded by several objects: furniture, cars, pets, humans, etc. Each of these objects have traits that we use to identify them. This is also the way eZ publish defines and manages content.
The system offers a selection of fundamental building blocks and mechanisms that together provide a flexible content management solution. An actual data structure is described using something called a content class. A content class is built up of attributes. An attribute can be thought of as a field, for example the "birthdate" field in a structure designed to store information about students. The description of the entire structure would be refferred to as the "student class". The characteristics of an attribute inside the class are determined by the datatype that was chosen to represent that attribute.
It is important to understand that a content class is just a definition of an arbitrary structure. In other words, the class itself describes the structure but it does not store any actual data. Once a content class has been defined, it is possible to create instances of that class. An instance of a content class is called a content object. Actual content is stored inside objects of different types. A content object consists of one or more versions. The versioning layer makes it possible to have different versions of the same content. Each version consists of one or more translations. The translation layer makes it possible to represent the same version of the same content in multiple languages. A translation consists of attributes. The attributes are the final elements in the content structure chain, this is where actual data is stored.
The content objects are wrapped and organized by the way of nodes that are placed inside a tree-like structure. This tree is often refferred to as the node tree.
Image26
