Static Content Generation Overview
You are here: Administrators Reference > Site Administration > Static Content Generation Overview


Static Content Generation Overview

The Static Content Generation module extends CommonSpot’s scalability, performance, and total cost of ownership benefit by enabling you to serve portions of your CommonSpot sites as straight HTTP, without the overhead of ColdFusion.  Separating the processes for handling dynamic and static content delivers a more scalable, reliable, and higher performance site.

Most site content is “semi-static” – changes occur infrequently enough to allow serving content in its currently stored state.  No dynamic retrieval or generation is required.  Under CommonSpot’s Static Content Generation model, pages of this type, with no other dynamic components, are generated as HTML at publish time and copied to a static subdirectory which mirrors the structure of the dynamic server. These static files are then served from one or more HTTP servers without the need for ColdFusion, reducing cost and increasing performance.

Mouseover to view larger

The typically smaller portion of the site that requires dynamic content (search results, pages with personalized content, pages requiring authentication, or pages with embedded, non-static custom scripts) are handled through a dynamic CommonSpot server.

Configuring a root-level site for static content requires a distinct server (either physical or virtual) for static content, and another for dynamic content. For example, the PaperThin site uses for dynamic content and for static content.


Related Links

Static Site Definitions

Example Site

Static Site Architecture

Cache/Static Settings

Initial Static Content Generation

Managing Static Content Generation

What Makes Content Dynamic?

Best Practices

Disabling Static Content Generation


You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of (requires login).

For technical support: