An eZ publish project can be treated similarly to a normal web application development project with one significant difference—the need for content. With web applications or traditional software development, there is little content; it is usually about data and that either already exists or will be entered by the users of the application. With eZ publish projects, content needs to be modeled, gathered, and entered into the system developed before it goes live. The problem is people aren't used to modeling and preparing content. Often it's left to the last minute, at which point the project has to be delayed as the content issues are not yet resolved. In a recent project, for a standard corporate website, the launch date was delayed by six months as the client worked on getting the content together. The key to success is in appropriate content modeling, and then gathering while the system is being built.