Skip to main content


A-Z glossary of PageSeeder concepts

Object model

One of PageSeeder’s main design strengths is how quick and straightforward it can be to import, edit and publish complex XML documents. The reason for this is PageSeeder’s object model (see document) and how it is used to represent XML data in an easily editable, generic form.

User interfaces vs User data structures

The conventional approach to XML editing software has focused on putting a user-friendly interface on the XML standard. However, given the limited adoption of XML tools, there is little support for this approach.

As an alternative to exposing XML to end users, PageSeeder uses the same approach as non-document web applications such as online banking or travel booking sites. That is, while data is stored in a rich data structure, when it’s served to the browser for editing, it is translated into HTML and Javascript. Upon submission, the data from the editing session is translated back to XML for management.

Because PageSeeder editors are expressed in HTML and Javascript instead of native XML, they can draw on commonly available UI frameworks such as jQuery. This dramatically improves developer productivity at the same time as providing a broad spectrum of options for users.

Using the editing capability of HTML in front of PageSeeder’s rich object model allows developers to implement complex XML publications with a minimal amount of code. Breaking large XML structures down to a collection of editable sections connected by PageSeeder’s advanced XLink architecture can substantially reduce the complexity of XML data. In turn, this simplifies the requirements of the editor.

Created on , last edited on