Static Site output guarantees that HTML is fully rendered at build time and remains readable without JavaScript. HTML is the source of truth.

React SSG uses React tooling and bundles even when pages are not hydrated. Static Site exists for content that must remain readable and durable without client frameworks or runtime assumptions.

Every page is a complete HTML document. Links use standard <a href>, and content remains readable without JS.

Enhancements such as search, copy code, and theme toggle are optional and capability-driven. They must never replace core content.

Enhancement scripts are included only when capabilities are detected. If no enhancements are needed, no JS is emitted.

Incompatible components degrade or emit warnings. Dynamic routes are skipped with explicit warnings to preserve determinism.

Code blocks render as semantic HTML with optional pre-highlighted output. Client-side highlighting is optional and policy-driven.

Content strings are parsed as lightweight Markdown. Headings feed the TOC, code fences map to code blocks, and links resolve against known routes.

CSS must establish layout, typography, and hierarchy. HTML must not rely on JS to look correct.

Static Site output uses semantic HTML, stable URLs, and optional sitemap and robots.txt generation for SEO.

Routing is filesystem-based with folder style output. baseUrl is resolved during lowering for subpath hosting.

Static Site avoids client-side routing, hydration, runtime data fetching, and framework-specific behavior. These are deliberate boundaries.