OpenACS 4 Subsites Design Document

-by Rafael H. Schloming
+OpenACS 4 Subsites Design Document

Prev	Chapter�10.�Kernel Documentation	Next

OpenACS 4 Subsites Design Document

By Rafael H. Schloming

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

*Note* This document has not gone through the any of the +

*Note* This document has not gone through the any of the required QA process yet. It is being tagged as stable due to high demand.

Essentials

OpenACS 4 Subsites Requirements

Introduction

An OpenACS 4 subsite is a managed suite of applications that work together for a particular user community. This definition covers a very broad range of requirements: from a Geocities style homepage where a user can install whatever available application he wants (e.g. a single user could have their -own news and bboard), to a highly structured project subsite with multiple +own news and forums), to a highly structured project subsite with multiple interdependent applications. Thus, flexibility in application deployment is the overarching philosophy of subsites.

Meeting such broad requirements of flexibility demands architecture-level support, i.e. very low level support from the core OpenACS 4 data model. For