A complete vinext static export

Build the experience.
Leave the server.

This site is an App Router and Pages Router application rendered ahead of time, then deployed as an assets-only site. Every linked content route exists before the first request.

An abstract island drawn as a contour map
Runtime requests
0
Deploy directory
dist/client
Worker code
none

What this example proves

Static does not mean inert.

01

Build-time React

Server Components run during vinext build and become durable HTML plus static RSC payloads.

02

Known dynamic paths

generateStaticParams expands dynamic and catch-all routes before anything is deployed.

03

Browser interactivity

Client Components hydrate normally, including state, effects, and query-string navigation.

04

Both routers

App Router generation and Pages Router SSG can coexist in one exported application.

generateStaticParams

Three slugs. Three real documents.

The dynamic route template never reaches production. Its known parameter values become concrete HTML files during the build.