Features
What ssg does, and where it stops
Each section says what the feature is and how to use it, checked against ssg 0.0.69.
A quality gate on every build
ssg build scores the site it has just built on ten pillars and writes the result to quality-gate-report.json in the output, with each issue named page by page. The build still writes the site when a pillar fails; this site's own build treats anything short of 10/10 as a failure.
Fifteen audit gates
ssg audit checks the built files. Its gates cover WCAG, JSON-LD, hreflang, language consistency, CSP and SRI, post-quantum TLS, HTML5, broken links, metadata, Markdown, a performance budget, AI discovery files, feeds, images and the search index. It exits with an error when a finding reaches the --fail-on level, which defaults to error, so it can stop a CI job. Results can be printed as text, JSON, JUnit XML or SARIF.
--skip-network is the default; --no-skip-network lets the link gate check external links too.
CSP and Subresource Integrity
Pages can carry a strict content security policy without hand work. The build moves inline <style> and <script> blocks into hashed files under _csp/, fingerprints local stylesheets and scripts, and gives each one an integrity value, which the audit's CSP and SRI gate then checks.
Content schemas
A content.schema.toml beside your content declares the front matter each kind of page must have. ssg validates every page that names a schema at build time, and stops with a named error when a required field is missing, instead of rendering a blank.
What a build produces
Besides the pages, one build writes RSS, Atom and JSON feeds, a sitemap and a news sitemap, a search index, llms.txt, a web manifest, an accessibility report and a CycloneDX software bill of materials. With [agents] in ssg.toml it also writes agents.txt and .well-known/ai-plugin.json, and with [edge_headers] a _headers file of security headers for Netlify and Cloudflare.
One-command deploys
ssg deploy --target <name> builds the site and ships it. The targets are netlify, vercel, cloudflare-pages, github-pages and s3, with tokens read from environment variables such as SSG_NETLIFY_TOKEN. The none target builds without uploading, for a dry run in CI.
A development server
ssg dev builds the site and serves it on https://static-site-generator.com, rebuilding when a file changes and pushing the change to the browser.
Themes
A theme is a directory of layouts. Name one with --theme <name> on the command line or theme = in ssg.toml, and ssg uses it as the template directory. The published themes, including Velocity, which this site uses, are on themes.static-site-generator.com.
Where it stops
The project's README is plain about the limits: ssg compiles ahead of time, so it does not suit pages that must be rendered per request; its theme ecosystem is small next to older generators; and its plugin API is pre-1.0 and may change between releases.