Glossary

A-Z glossary of PageSeeder concepts

PageSeeder design objectives

Introduction

PageSeeder approach to XML publishing workflows is completely different than that of conventional applications. Because PageSeeder was conceived and implemented as a web-based platform, it was designed for a different set of constraints and infrastructure than desktop applications.

Also, having deep experience with conventional publishing tools, PageSeeder's architects knew that the conventional approach to XML was too complicated, therefore, too expensive for most organizations. Having watched as the largest and best resourced developers of publishing tools were only able to gain minimal traction with XML, there seemed to be little reason to simply move the conventional single-user architecture to the web.

With this in mind, PageSeeder was created to meet the following design objectives:

  • Process document structures of any complexity. PageSeeder takes the simplicity of a wiki and extends the architecture to address highly complex documents.
  • Provide collaborative editing and review – the slow rate of change in traditional, single-user desktop software indicates that architecture has been exhausted for productivity gains.
  • Focus on the needs of developers – having spent many years implementing publishing solutions for end-users, the architects knew that the real problem for publishing was that end-user requirements are too diverse for general solutions and that the real opportunity was in productivity (see tools for developers).

Knowing that the conventional model of one document = one file would never work in a collaborative

Created on , last edited on