Book Image

Managing eZ Publish Web Content Management Projects

Book Image

Managing eZ Publish Web Content Management Projects

Overview of this book

open-source CMS (content management system) and development framework with functionality for web publishing, intranets, e-commerce, extranets, and web portals. In this book, Martin Bauer of designit.com.au an eZ publish Silver partner, teaches you how to successfully manage and implement an eZ publish web content management project. He shows you how to produce quality results in a repeatable manner with the minimum of effort, and end up with eZ publish solutions that will delight your clients. The book presents strategies, best practices, and techniques for all steps of your eZ publish project, starting from client requirements, through planning, information architecture and content modeling, design considerations, and right up to deployment, client training, maintenance, support, and upgrades.

Related Content you might be interested in

Current Title:

Small book image
Managing eZ Publish Web Content Management Projects
Oct, 2007 | 320 pages
No titles found
Table of Contents (20 chapters)
Managing eZ Publish Web Content Management Projects
Managing eZ Publish Web Content Management Projects
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
Preface
Preface
Free Chapter
1
Understanding Web Content Management
Understanding Web Content Management
Why Use a Content Management System?
Content Management versus Development
Myths
Types of Websites and Web Applications
Web Solution Categories
What does All This Mean for eZ Publish Projects?
Summary
2
Information Architecture and Design
Information Architecture and Design
Information Architecture
Five Facets of Design
3
eZ Publish Overview
eZ Publish Overview
What is eZ Publish?
Internal Structure and Configuration
The Lego Approach
Data Types, Content Classes, and Objects
Structuring Content
Sections
Templates
Template Override System
Designs
Access Control
Workflow
Extensions
Summary
4
Defining an eZ Publish Project
Defining an eZ Publish Project
Requirements
Project Brief
Project Brief—The White Angel Foundation
Planning Workshop
Estimation
Summary
5
How to Write a Specification
How to Write a Specification
Content Model
Users and Groups
Features
Site Map
Content Classes and Rules
Custom Templates
Screen and Performance Standards
Specification Process
Creative Brief
Summary
6
Content Modeling
Content Modeling
The Purpose of a Content Model
What Makes a Good Model?
Defining a Content Model
Summary
7
Planning and Pricing
Planning and Pricing
Project Planning
Pricing Your Project
Summary
8
Risk Management
Risk Management
Key Steps in Risk Management
Types of Risks
Risk Management in Practice
Shooting the Messenger
Key Risks in eZ publish Projects
Summary
9
Open Project Management
Open Project Management
Manifesto for Agile Software Development
Individuals and Interactions over Processes and Tools
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation
Responding to Change over Following a Plan
Open Management Practices
Summary
10
Implementation
Implementation
Infrastructure
Version Control
Setup
Configuration and Development
Moving Code between Environments
Content Gathering
Content Population
Summary
11
Testing
Testing
Load Testing
Summary
12
Training
Training
Standard User Training
Custom Training
User Manual
Technical Training
Summary
13
Maintenance and Support
Maintenance and Support
Patches
Upgrades
Enhancements
Support
Summary
Appendix A
Appendix A
The White Angel Foundation Functional Specification
Table of Contents
Revision Control
1 Introduction
2 Site Map
3 Standard Features
4 Page Structure
5 Media Library
6 Users & Roles
7 Custom Features
8 Browser Compatibility
Index
Index

Template Override System

The beauty of the template system is that you only have to change the elements that you want to. If you're happy with the default templates, then all you need to do is create your own stylesheet to make it look how you want it to.

If you need to change the HTML produced, then you can create an override template that the system will use in place of the default template.

You can then decide under what conditions that template will be used. For example you could create an override template that is used for:

  • All pages within a section

  • A particular content class

  • A particular node

  • When a user has logged in

To get the system to use an override template, you create an override.ini configuration file and define the conditions for when that override template is to be used. E.g. if we want to use a particular template for all news items, we would include the following block in the override.ini file:

# Override for news items folders
 [news]
 Source=node/view/full.tpl
 MatchFile=news...
Previous Section
End of Section 9
Next Section