There are many free and commercial packages providing the essentials of a website.  These are constructed by professional graphic artists and designers and can provide a polished look and feel to a Web presence while saving a significant amount of effort for the site administrator.

A simple Web search, such as for "website template package", can locate many such resources.

It is usually a relatively straight-forward exercise to adapt these templates to VWcms.  Such packages are often available as ZIP archives and contain files representing the site components.  One such example is shown below.

$ unzip -l EXAMPLE.ZIP
Archive:  VWCMS_ROOT:[000000]EXAMPLE.ZIP;1
  Length     Date   Time    Name
 --------    ----   ----    ----
    17107  02-06-11 21:34   license.txt
      306  02-06-11 21:34   images/img01.jpg
     6838  02-06-11 21:34   index.html
     5406  02-06-11 21:34   style.css
 --------                   -------
    29657                   4 files

These components need to be extracted into the area of the file system reserved for the site and then configured to conform to VWcms requirements.  The basic steps required are listed below.  Of course all templates will vary more or less in content and structure and require some thought, and possibly experimentation, to achieve the desired result.  It is recommended to get the basics of the site configured and edited before continuing with the finer detail.

1. Map the proposed site into the server's web-space.

   # WASD_CONFIG_MAP pass /_example/* /vwcms_root/example/*
   map /example/* /vwcms/example/*
   map=once script+ /vwcms/* /cgi-bin/vwcms/*
   
   $ HTTPD/DO=MAP
   

2. Check the structure of the archive, in particular if it contains a top-level directory.

   $ UNZIP -l <location>:EXAMPLE.ZIP
   

3. If required, create a directory with protections appropriate to the server and make that the default.

   $ CREATE /DIRECTORY VWCMS_ROOT:[EXAMPLE] /PROT=W:RE $ SET DEFAULT VWCMS_ROOT:[EXAMPLE]
   

4. Unzip the website package archive (then SET DEFAULT to the package subdirectory if required).

   $ UNZIP <location>:EXAMPLE.ZIP
   

5. Copy the VWcms starter-kit content file and the style-sheet file from the VWcms kit.

   $ COPY WASD_ROOT:[SRC.VWCMS.STARTER]_INDEX.HTML * $ COPY WASD_ROOT:[SRC.VWCMS.STARTER]_VWCMS.CSS * 

6. Ensure the protections for all files are adequate.

   $ SET PROTECTION=W:RE [...]*.*
   

7. Generally the template content is in a file named INDEX.HTML.
   This site path should now be able to be accessed and the unmodified package content viewed.
   This also checks the path mapping.
8. The INDEX.HTML must be made the site template file.

   $ RENAME INDEX.HTML _SITE.HTML 

9. Map the site into VWcms configuration.

   # VWCMS_CONFIG
   [if-CGI-request_uri] /example/*
   [site-directory] VWCMS_ROOT:[EXAMPLE]
   [site-name] example
   [endif]
   

10. Edit the _SITE.HTML template file.
    1. Add VWcms style-sheet link below existing style-sheet link. Modify other links as required.

       <link href="style.css" rel="stylesheet" type="text/css" />
       <link href="_vwcms.css" rel="stylesheet" type="text/css" />

    2. Substitute $$CONTENT$$ for the template content or in the desired location of the content.
    3. Similarly replace any template table-of-content with $$TOC$$ or place where desired.
    4. Add $$LOGIN$$ and $$MANAGE$$ directives somewhere convenient allowing the site to be edited and managed.
11. Access the site and work out what you've missed  :-)
12. Using VWcms populate the content of the site
13. If $$PRINT$$ is used a template will need to be customised.

    $ COPY WASD_ROOT:[SRC.VWCMS.STARTER]_PRINT.HTML * /PROT=W:RE
    

Fundamental Directives

$$CONTENT$$  $$LOGIN$$  $$MANAGE$$  $$TOC$$

Common Directives

$$AGO$$  $$BACK$$  $$$LASTMOD$$  $NEXT$$  $$PREV$$  $$PRINT$$  $$TIME$$  $$TITLE$$