The Content Model
Content is organised in a tree of directories; this doesn't necessarily have to correspond with how content is navigated in any particular medium (depending on how the navigation is configured).
Content consists of features, each of which may have one or more feature pages. The meaning of multiple pages within a single feature is flexible; it could be used to implement local navigation of groups of pages, or multi-page stories with "next" and "previous" page buttons, and so on.
Multiple Page Versions
In common with almost all content models, the OCE allows more than one version of each page. Each version is either authorised for publication or is not, and is also associated with an "effective" date, allowing content to be authorised ahead-of-time and to automatically appear at the scheduled moment.
The content of a page version is made up of several ordered page components. Each type of page component corresponds to a package of code and a related template which contains the logic for rendering. Thus, as well as editing static copy using page components such as "BodyLeft", users can place and configure dynamic components wherever they wish.
Copy entered into the OCE is a basic form of rich text, which allows a limited range of styling details to be added. Text, paragraphs, line breaks, bold, italic, hyperlinks and images are allowed (without, say, allowing users to edit markup directly), so the look and feel cannot be broken, and content is guaranteed to be presentable across many media.
The content model also stores a list of named metasections, which are loosely defined as "abstract groupings of content". Each feature may be assigned to one or more metasections. These "hooks" are used by the navigation model to define which types of content are allowed to appear in which sections of a site, and can also be an aid to searching and organising content.