Authoring architecture

The authoring architecture describes what types of content will be required for the site and what change management strategies will be applied when updating content and design. We need to define:

• Authoring templates required
• Workflows to manage changes
• Library folders used to group items

Library architecture

The library architecture describes where we will store the content items. For example, we could split the site between the items that control the look and feel of the site, such as presentation templates and components, from the content of the site. We could also separate the libraries into different team libraries such as "human resources" and "support".

Authoring templates

We need a separate authoring template for each type of content item and site area used by the site. The list of authoring templates defined in the authoring architecture is based on the different page types identified in the project plan, analysis document, and prototype website.

The information specified for each authoring template includes:

• Which content type to use. For example:
  • A site area for a parent item
  • A content item for the children of the parent item
  • A site area for a sub-section of a parent item

• For the authoring template itself:
  • Name
  • Display title
  • Description
  • Template type
  • Access settings

• Default form settings including:
  • Default presentation template, if required
  • Default style sheet, if required
  • Form layout
  • Whether editors can manage elements
  • Actions to hide
  • Where to save items
  • Help text
  • Versioning strategy

• Default content and fields for the item:

  • Name and field display options

  • Display title and field display options

  • Description and field display options

  • Required elements
    • HTML design for any default element content
    • Default parameter selections for any component parameters
    • Field display options

• Default properties for each item:
  • Any default profiling and field display options
  • Any default workflow parameters and field display options
  • Any default access settings and field display options
  • Field display options for the History section

Workflows

We use workflows to control the access to, verification of, and eventual approval of items. Only if an item is approved at all stages up to a published stage can it be viewed on the website. Use a workflow to:

• Review the accuracy of content
• Review content for any legal implications
• Review content to ensure it meets accessibility guidelines
• Ensure that no malicious code such as cross scripting attacks have been added to content

Each workflow, workflow stage and workflow action required for the web content system is listed in the authoring architecture.

Folders

Folders are used to group sets of item types into logical groupings. This is useful when we have large numbers of items in the library and want to distinguish between different groups of items within each item type view. Each folder required for your web content system is listed in the authoring architecture. For example, we could use a set of folders to groups different sets of image components:

• Logos
• Diagrams
• Staff photos
• Product photos

Version management strategies

We can configure your system to either automatically save a version of an item each time it is published, or allow users to select when to save a version of an item. The version management strategy for different item types are documented in the authoring architecture.

Parent Create a design document

Related concepts:

Content libraries
Users, Groups and Roles
Work with folders
Workflow and change management
Manage versions of items