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.