Authoring - The content architecture

HelpServer's architectural design models content extremely well. You can easily structure content by breaking it up into separate objects that you can then access independently.

The nodes in HelpServer's content tree can be actual content objects themselves or they can be other structures (folders). You create a content object of any type and then assign “child” objects to it, which can also have child objects, and so on. You can also designate properties or settings to a node and then apply it to content below it.

This approach allows you to relate information by easily associating pieces of content with each other. You do this by putting a piece of content in a certain place in a content tree or by stating that a certain property of a content item is a reference to another object somewhere in the system.

The structure of content, the tree, is itself accessible: you can navigate on it and you isolate actions on branches of the tree (for example, search from a node down).There are several methods and criteria for retrieving content from the repository. It can come back in a neutral format with clear information about its context. You can see exactly where in the tree the object is from, its path to the root of the tree; and the branch or branches where it is located.


 About HelpServer
 About HelpServer
 The Workbench
 The web portal
 The server
 The content architecture
 The people involved
 Starting up and logging on
 The basic working principles
 Using the content in help and documentation systems
 Formatting the content
 Searching and replacing text
 Reusing content with shares
 Navigating with hyperlinks
 Navigating with pointerpaths
 Using bookmarks and jumps
 Duplicating content with clones
 Using tables
 Including media files
 Navigating to web pages
 Using embedded chunks
 Including html code
 Navigating with menus
 Using snippets
 Spelling checking
 Using the view mode
 Creating an index
 Creating a FAQ
 Creating a glossary
 Team authoring
 Working with projects
 Setting up structured authoring
 Generating file based output
 Creating printed output
 Importing files and folders
 Loading files in the project gallery
 Converting legacy content
 Including legacy content in real time
 Transferring objects between installations
 Customizing the look and feel
 User accounts
 Working with templates
 Working with metadata
 Workflow management
 Using event exits
 Appendix A: The URL parameters
 Appendix B: The object indicators
 Appendix C: Play Javascript