implementation is built with StrataCode from the source on github. It's a single layer bundle used to build two configurations for use on the site. One is a static html/javascript website to provide the majority of the content. The other part supports the download forms and analytics.

The static website is built with this command: scc -c doc/clientOnly
The -c option means "compile only". In the build directory, by default /usr/local/scMain/build/doc_clientOnly, will contain the 'web' directory that has the html and javascript files served by the web server (nginx). It includes Javascript to implement some of the dynamic navigation features. Other content sections that depend on server features but with tags using exec="server". In the static website, they are rendered at compile time. In the server only version, they are rendered by the server when the page is requested.

The dynamic version of the site supports the download forms and event tracking. It's built with a different original layer but uses the same layers for the content part of the site. scc -c doc/webConfig The webConfig layer is in a private bundle called "deploy". It modifies the downloadManager class replacing the download codes to keep them secret. It also contains the ssl keys and other secure deployment info. This layer is defined with:

file: doc/webConfig/
doc.webConfig extends doc.forms,, servlet.options.disableRealTime {
The development version can be compiled and run with just the doc.forms layer: scc doc.forms

This command also generates a script called startSCJetty in the build directory to run the server standalone, without the dynamic runtime. The mode is more appropriate for a production deployment and has a smaller memory footprint.

The test suite contains a few more configurations for running the site:

client/server with sync: scc js.schtml js.sync doc.core

In dynamic mode for refresh after changes: scc -dyn doc.core