This screenshot shows a user editing the HTML/Template for a page. The syntax highlighting editor helps you to write valid HTML and any changes are auto-saved every few minutes so that you can easily retrieve earlier versions of the page.

Click the image to zoom in.

This screenshot shows a user editing the script that runs whenever the page from the previous screenshot is invoked.

The syntax highlighting editor helps you to write valid Javascript and your changes are saved every few minutes so that you can easily retrieve earlier versions of the script.

For every incoming request a global script is run and then a script specific to the requested page (shown here) is run helping you to avoid duplicating code but also allowing you to improve performance by isolating slow scripts.

Click the image to zoom in.

This screenshot shows the template page that is generated when you create a new website or a new page within a website.

The page provides links to basic documentation on Chrome Server. It also provides links to the administration control panel pages and (in the top right corner) a button reaidng "Edit Me" that takes you directly to the part of the control panel allowing you to edit the page's content.

The template page is styled purely with CSS so altering this to suit your own needs is very straight forward. As a starting point you can use the existing HTML, the existing CSS, or completely replace both with your own content.

Click the image to zoom in.

This screenshot shows a view of the application log for a website.

The application log tracks script failures (including the line number of the script where this is available). It also tracks less serious issues that would not cause user-visible errors such as missing variables used in the page template - for example the symbol ${foo} used in the page template with no corresponding foo Javascript variable in the scripts.

In addition to the entries placed in the application log automatically you can add logging commands to your own scripts to record information as you see fit. You can associate any one of five logging levels to these entries: fatal, severe, warning, informational, and debugging.

Click the image to zoom in.

This screenshot shows a view of the statistics log for a website.

The statistics logs track the number of times each page is requested, the overall performance of the page (calculated as the number of milliseconds taken to return the page contents to the user), and the number of errors or warnings that have occurred during requests for that page.

The performance metric (measured in milliseconds) combined with the number of requests received gives you an indication of where to concentrate your efforts should you choose to optimise the performance of parts of your website.

Click the image to zoom in.