Key components
Below are some of the key elements you'll need to put into a simple database.

Owner field (Author)
This field will control access to the content itself, which is critical on sites requiring security. Make this an author field and list the content owners for this page in this field.

Title field (Plain Text)
The title field is necessary for sorting and organizing the page within a Notes database for easy access by content owners and other stakeholders.

Body field(Rich Text)
The body field is where the actual content for the page resides. The Body Field is what will actually be displayed on the Web. This is a rich text field that can contain images, files, tables, text, etc.

Category field (Keyword-optional)
Category fields are excellent for categorizing the pages into logical groups to make access easier. Response forms are also an excellent way to group like pages.

Other considerations
In designing a DCM site keep in mind that there are two designs at work: one for Web browsers (your readers) and one for content owners (your editors and writers). That said, using a form formula in a view can allow for the use of different forms for Web and client usage. Hidden text areas can accomplish a similar goal.

Site organization
Organizing and structuring a Web site for distributed content management adds an extra level of complexity to a site. Rather than simply structuring the site for viewing, it must also be structured logically for content editing and updates. The two structures will not necessarily fit easily together, which is not a problem -- merely an added challenge.

A Domino Web site may consist of multiple Notes/Domino databases that are cross-linked to each other via navigators, links, outlines, etc. To the Web browser user, where the content resides on the server is irrelevant. However, for the content owner, this does matter. Content owners need to know exactly where their pages are in the greater scheme of the entire site. This is a critical component of successful distributed site-content; access must be simple and straightforward. If it's not, it's less likely to be used.

Process!
Management of a distributed site must also take into account the processes and workflow necessary to keep content accurate and up to date. Accomplishing this involves mapping content approval workflow to the needs of the business. Similarly, content updating must be integrated into the job processes of the content owners. Both of these elements need to be as seamless as possible.

Mapping content approval could be as simple as requiring a manager's sign-off on a content change before it's made live on the site. In the same vein, a larger organization might require a much more complex affair involving numerous managers and reviewers before the site can go live. Notes workflow must mimic and follow these process requirements.

Like any other business process, content ownership must be integrated into the job requirements and processes of the individual content owners. Whatever the event is that may trigger a content change for a Web site, that event should become the impetus for the actual content change itself.