This starter is configured for static output, which keeps deployment simple. The build step produces prerendered HTML for the landing page and the full docs tree.
Local production build
Use the standard Vite+ command:
vp run build
That command builds the workspace packages, then runs through Void, resolves the routes, and emits static output because void.config.ts opts into static mode.
Why static output fits this starter
The first version does not depend on:
- database reads
- auth state
- API routes
- runtime personalization
That means the site benefits more from simplicity than from dynamic rendering.
Deployment checklist
Before publishing, verify a few basics:
- Internal links move cleanly between docs pages.
- Title and description metadata are present for the important routes.
- The generated output includes every planned page under
/docs/*.
What to add later
If the site eventually needs search, auth-protected pages, or dynamic examples, you can expand the architecture later. Starting static gives the content model time to settle before operational complexity increases.