The Publishing Model

Distributed Authoring

Distributed Authoring facilitates the appropriate distribution of authoring, publishing and support responsibilities by separating content from presentation and documents from navigation, in a quality managed environment.

The key benefits of this are that:

• control of documents is retained by content authors, saving both cost and time.
• a document can be accessed from multiple entry points (sites), which means updating site content is faster and easier, and requires editing of only one document.
• documents from a single content library can be published to multiple sites.
• expensive programming expertise is not required for day-to-day updates or additions to the site.
• document control, security and archiving facilities are managed by the system.
• the three step publishing process (Author/Review/Approve) minimises the risk of inappropriate material being published.
• navigation can be easily amended and updated, and is designed to facilitate multiple entry points (sites) to the same content.
• highly scalable architecture can grow with an organisation’s information resource requirements.

Content Quality Management Process

The system provides a multi-tiered content quality management process for use in the publication of web content. This is achieved through an electronic publishing facility that manages and tracks the ‘life-cycle’ of a document within the content quality management process. The five primary stages of the cycle are:

• Author - creating a new document, a new version of a document, a clone of a document.
• Review – a configurable workflow process selected either based on a field (e.g. Business Unit) or from a list.
• Publish - packaging of the content, metadata and resources from the content libraries to the site navigators (or external application).
• Launch – the final site quality inspection process which makes content visible to users
• Version Control & Archiving – tracking complete versions (including metadata). Providing for off system storage and retrieval, (including VERS compliance).

The business rules e.g. once “published” a document cannot be deleted, only archived; manages the process. While the process queue ensures the integrity of the system, e.g. updating the document status in the content library once the document is launched at a remote site.

Dynamic Site Rendering.

Content on the site is dynamically rendered – bringing together content (content, metadata and resources) with structure (sites, subsites, navigation and menus) and applying design (site skins, layout and style).