SSG ​

Static Site Generation. This is similar to SSR. But with SSG the server renders pages only once in a build step, not on each request.

Advantages are:

• As with SSR, the pre-rendered page content is more rapidly visible.
• Like client side rendered web apps, SSG apps can be served from a simple static web server.

This requires that the contents of the site do not depend on the user context. I.e. redeployment is the only way to update the content. This is typically true for a blog or documentation site.

Then a static web server is enough to serve the pre generated pages. No JavaScript is executed on the server side after the Static Site Generation build. This build step is completely independent of the server that later hosts the generated files.

As with SSR, the static pages are hydrated once loaded to the browser. It is also possible to include dynamic content, e.g. fetching and including CMS content via JavaScript. But that is obviously not statically generated than.