Static HTML sites

Use HTML for content that Nginx can serve directly without PHP-FPM or a persistent Node process.

Plain files

Create the site without a repository, then use the file manager or another trusted transfer method to place index.html and its assets in the configured web directory.

This is the leanest site type: Nginx serves files directly and there is no application daemon.

Git-backed static site

Connect a repository and branch to deploy versioned static content. If the repository includes package.json, the default script uses npm to install dependencies and run the optional build command. For framework-specific package-manager control and output-directory settings, use a Node.js site in static mode.

Deployment modes

Standard deployment updates the Git checkout in place. Zero downtime clones into a timestamped release and switches the current symlink after the optional build succeeds.

Set the web directory to the directory Nginx should serve. Ensure it matches the output generated by the repository; a successful build with the wrong web directory can still produce a 404.

When to choose Node.js static mode instead

Choose Node.js > Static build when you need:

• npm, pnpm, Yarn, Bun, or no-package-manager selection
• A configurable build command
• Next.js, Nuxt, or generic output-directory defaults
• Node toolchain readiness validation during site creation