- Remaining Developer Guides and Upgrading - SilverStripe in a namespace or api has not been change - To keep PRs easier no formatting was changed Update merge conflics with two files Update Silverstripe Ltd, Silverstripe Cloud and Silverstripe CMS Silverstripe CMS Ltd > Silverstripe Ltd Silverstripe CMS Platform > Silverstripe Cloud Silverstripe CMS Framework > Silverstripe CMS Resolve merge conflict Remove Framework from Silverstripe CMS Framework - 3 files Change SilverStripe CMS to Silverstripe CMS
1.1 KiB
title | summary |
---|---|
Static Publishing | Export your web pages as static HTML and serve the web like it's 1999. |
Static Publishing
One of the best ways to get the top performance out of Silverstripe CMS is to bypass it completely. This saves on any loading time, connecting to the database and formatting your templates. This is only appropriate approach on web pages that have completely static content.
[info] If you want to cache part of a page, or your site has interactive elements such as forms, then Partial Caching is more suitable. [/info]
By publishing the page as HTML it's possible to run Silverstripe CMS from behind a corporate firewall, on a low performance server or serve millions of hits an hour without expensive hardware.
This functionality is available through the Static Publisher with Queue module. The module provides hooks for developers to generate static HTML files for the whole application or publish key pages (e.g a web applications home page) as HTML to reduce load on the server.