This background is for the site designers as well as all page authors.

These are the pages which rarely appear in the table of contents but are vital to the appearance of the site.  They are normally Hidden.  The first are the pop up pages we mentioned earlier, the second are pages whose top content is used on other pages or in templates via the |.pContent:##.| tag.  The third are response form sections which the Admin user can create for use on specific pages.   Since the "Show Special" link will display these pages' (as well as the pages with a display order of 1-1) titles and the sections they are in, it is probably useful to organize them into descriptive sections.

Pop-up Pages are created like normal pages but all their content areas are displayed one after another in a central section (for this reason the top section is normally the only one used).  The style sheet from the default template is use but the rest of the page is simple. At the top right is a Java-script powered Close button, below that is the contents of the content area.  Only |pContent:#.| and |.Year.| tags are interpreted. 

pContent pages: These pages use only their first content area.  They are called to provide common information to several pages, or where a the content is maintained by an author who does not have permissions to edit the page.   They are useful to ensure the same information is available on several pages. If the information is changed it will update all pages which contain the proper pContent tag without having to generate a new version of the page (and publish it).

Form Pages: are a special class of pContent pages.  These pages present forms for the visitor to fill out and then an email is sent containing that information either to a predetermined address or through the use of the optional Contact table, any of several addresses. They are created by the Admin user by selecting the 'Form' radio button.  They are described in the Administrator/Site setup section later in this help.

Common part of pages: Pages all contain information which may change periodically (e.g., common page headers and footers). Rather than burying them in templates which have to be edited individual, these elements are put in a separate section (e.g, ~pageBits) which you can edit.