A composite site is one that spans multiple directories, using shared templates and $$GOTO$$ to integrate the tables-of-content.

This allows multiple, independent site management domains to provide an effective, tightly-integrated single site.

The following describes such an example.

Primary Site

This site is the primary entry point for the web presence.

Among other content it has two sections, one titled "Sales" containing a $$GOTO$/sales/$$, and the other "Products" containing $$GOTO$/products/$$.  Each of these will redirect to the respective mapping.

Secondary Site "Sales"

This site provide a semi-independent collection of sales-related resources.

This and other secondary sites would contain a section titled "Home", or other appropriate term to identify the primary site, containing $$GOTO$/$$ to redirect to the home page.

A secondary site would generally use the primary configuration to supplement it's own configuration.  This allows a minimum of directives in the secondary with only the primary requiring configuration for integrated site requirements.  Secondary sites locate the primary configuration using the global configuration file.  For this example

# global
[site-directory]  VWCMS_ROOT:[SALES]
[site-config]  VWCMS_ROOT:[ACME]_VWCMS.CONF

Secondary sites use the site and print templates of the primary site.  This is accomplished using the following directives in secondary sites' site configuration files.

# site
[site-template]  VWCMS_ROOT:[ACME]_SITE.HTML
[site-print]  VWCMS_ROOT:[ACME]_PRINT.HTML

Secondary Site "Products"

This site provide another semi-independent collection of resources with the same configuration requirements as the first secondary.

Global Configuration

The following configuration assumes a VWcms root logical of VWCMS_ROOT.

[if-CGI-path_info]  /acme/*
[  site-directory]  VWCMS_ROOT:[ACME]
[if-end]
[if-CGI-path_info]  /sales/*
[  site-directory]  VWCMS_ROOT:[SALES]
[if-end]
[if-CGI-path_info]  /products/*
[  site-directory]  VWCMS_ROOT:[PRODUCTS]
[if-end]

Server Mapping

Of course each secondary site, as with each primary site supported, must have a mapping for the server to locate the respective resources.

For the above example and for the WASD package these would be

pass /_acme/* /vwcms_root/acme/*
map /acme/* /vwcms/acme/*
pass /_sales/* /vwcms_root/sales/*
map /sales/* /vwcms/sales/*
pass /_products/* /vwcms_root/products/*
map /products/* /vwcms/products/*

Site Directories

Although the above example shows the file-system location for the sites as peers there is no reason why a secondary site cannot be located as a subdirectory of the primary site.