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

Upgrades

Upgrades have the same options as patches: you can do it yourself or pay for the eZ network solution, which includes upgrades.

As with patches, our experience has been with manual upgrades only. We aim to have each solution upgraded once a year; however, sometimes a client will choose not to upgrade their site as there is no new functionality in the latest release that they feel that they need; on the other hand, some want to upgrade or we recommend for them to upgrade as the latest release includes a feature that they can take advantage of.

When considering an upgrade, we tend to not go for the very latest release; they usually have bugs that are yet to be fixed or discovered. E.g. rather than upgrading from 3.5 to 3.6, we kept waiting until 3.6.1; this version was more stable and the inevitable bugs from a new point release had been fixed.

It's important to note that releases are cumulative. You can't pick and choose to simply jump several versions in an upgrade without considering...

Previous Section
End of Section 3
Next Section