mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-09-18 23:46:21 +02:00
6888901468
* First cut * Temporarily disable composer.json for netlify build * POC * New recursive directory query, various refinements * Fix flexbox * new styled components plugin * Apply frontmatter delimiters * Mobile styles, animation * Search * Redesign, clean up * Nuke the cache, try again * fix file casing * Remove production env file * ID headers * Move app to new repo * Add frontmatter universally * Hide children changelogs * Add how to title * New callout tags * Revert inline code block change * Replace note callouts * Fix icons * Repalce images * Fix icon * Fix image links * Use proper SQL icon
21 lines
1.1 KiB
Markdown
21 lines
1.1 KiB
Markdown
---
|
|
title: Static Publishing
|
|
summary: 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 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](partial_caching) is more suitable.
|
|
[/info]
|
|
|
|
By publishing the page as HTML it's possible to run SilverStripe 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](https://github.com/silverstripe/silverstripe-staticpublishqueue) 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.
|