eZ Publish Overview | Managing eZ Publish Web Content Management Projects

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Managing eZ Publish Web Content Management Projects

4 (1)

Managing eZ Publish Web Content Management Projects

4 (1)

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.

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

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

Information Architecture and Design

Information Architecture and Design

Information Architecture

Five Facets of Design

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

Defining an eZ Publish Project

Defining an eZ Publish Project

Requirements

Project Brief

Project Brief—The White Angel Foundation

Planning Workshop

Estimation

Summary

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

Content Modeling

Content Modeling

The Purpose of a Content Model

What Makes a Good Model?

Defining a Content Model

Summary

Planning and Pricing

Planning and Pricing

Project Planning

Pricing Your Project

Summary

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

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

Implementation

Implementation

Infrastructure

Version Control

Setup

Configuration and Development

Moving Code between Environments

Content Gathering

Content Population

Summary

Testing

Testing

Load Testing

Summary

Training

Training

Standard User Training

Custom Training

User Manual

Technical Training

Summary

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

Structuring Content

In eZ publish, content is structured using nodes and locations. Nodes are the tree structure that we normally would refer to as the site map. As there are times when we want to have a piece of content in more than one place in the site, an object can have multiple locations.

Nodes and Locations

The content structure in eZ publish is created by nodes. Each node represents a part of the site. A publish object is then associated with a node to be a part of the content structure.

E.g. Node ID 5 is associated with object ID 47.

This approach allows an object to be moved from one node to another without upsetting the site structure.

Locations

Objects can be associated with more than one node so that a particular object can appear in more than once place within the content structure. Each location is a combination of a node and an object.

For example, a particular object (in this case, a news item) can be found in the news section (presented by node ID 54) and in the press release...

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Managing eZ Publish Web Content Management Projects

Search

Your notes and bookmarks