By Rafael H. Schloming and Dennis Gregorovic
OpenACS docs are written by the named authors, and may be edited
by OpenACS documentation staff.
The following is a requirements document for OpenACS 4 Subsites, part of the
@@ -9,22 +10,22 @@
intranet/extranet website serves both units within the company (e.g.,
offices, departments, teams, projects) and external parties (e.g., customers,
partners, vendors). Subsites enable a single OpenACS instance to provide each
-subcommunity with its own "virtual website," by assembling OpenACS
+subcommunity with its own "virtual website," by assembling OpenACS
packages that together deliver a feature set tailored to the needs of the
subcommunity.
The OpenACS subsite system allows a single OpenACS installation to serve multiple
communities. At an implementation level this is primarily accomplished by
-having an application "scope" its content to a particular package
+having an application "scope" its content to a particular package
instance. The request
processor then figures out which package_id a particular URL references
and then provides this information through the ad_conn api ([ad_conn
package_id], [ad_conn package_url]).
The other piece of the subsite system is a subsite package that provides
-subsite admins a "control panel" for administering their subsite.
+subsite admins a "control panel" for administering their subsite.
This is the same package used to provide all the community core functionality
-available at the "main" site which is in fact simply another
+available at the "main" site which is in fact simply another
subsite.
Use-cases and User-scenarios
The Subsites functionality is intended for use by two different classes of
users:
Package programmers (referred to as 'the programmer') must
develop subcommunity-aware applications.
Site administrators (referred to as 'the administrator') use
-subsites to provide tailored "virtual websites" to different
+subsites to provide tailored "virtual websites" to different
subcommunities.
Joe Programmer is working on the forum package and wants to make it
subsite-aware. Using [ad_conn package_id], Joe adds code that only displays
forum messages associated with the current package instance. Joe is happy to