Skip to main content

Static Site Deployment: Build, Hosting, Domain, and Launch

The biggest advantage of a static site is that the launch chain is relatively simple. But simple does not mean you can skip understanding it.

What You Are Actually Deploying​

For sites like Docusaurus, Hugo, and Astro documentation sites, what goes live in production is the build output.

That is the set of static files you get after running the build, such as:

  • HTML
  • CSS
  • JavaScript
  • Images
  • Fonts

The Minimum Chain for Launching a Static Site​

Local content
  ↓
Build command
  ↓
Static output
  ↓
Hosting platform / Object storage / Nginx
  ↓
Bind domain
  ↓
Configure HTTPS / CDN

Separate the Stages Clearly​

1. Build​

For example:

npm run build

The goal of this step is to convert source code and content into directly accessible static files.

2. Hosting​

There are usually three approaches to hosting static files:

  • Static hosting platform
  • Object storage + CDN
  • Your own Nginx server

3. Domain Binding​

Let users access your own domain instead of the platform's default domain.

4. HTTPS and Caching​

Keep the chain secure and give static assets appropriate caching policies.

Why Static Sites Are Good For a First Website​

Because you do not need to solve these first:

  • Long-running processes
  • Application crash recovery
  • Database migrations
  • Backend dependency deployment
  • Server permissions and runtime security

This lets you focus on getting the full "launch a complete site chain" working first.

What To Focus On When Choosing Hosting​

1. Is Your Site Purely Static?​

If so, prefer static hosting. Do not jump to a server first.

2. How To Connect a Custom Domain​

You need to confirm:

  • Whether to use an A record or CNAME
  • How to handle the bare domain vs. www
  • Whether the platform automatically issues certificates

3. Whether the Build Output Path Is Stable​

This affects:

  • Whether static assets return 404
  • Whether sub-path deployment is correct
  • Whether CDN caching is stable

At Minimum, Check These Things Before Launch​

  1. Local build succeeds
  2. Resource links in the build output are correct
  3. Custom domain is already working
  4. HTTPS works properly
  5. Deep pages beyond the homepage are directly accessible
  6. After refreshing, no 404s or broken resource paths appear

Static Sites Are Not Without Pitfalls​

1. HTML and Static Asset Cache Policies Are Not Separated​

This easily causes the homepage to not update promptly.

2. Custom Domain Is Connected, But Only One Subdomain Is Configured​

This causes inconsistent behavior between the bare domain and www.

3. Assuming Platform Hosting Means You Do Not Need to Understand DNS​

The key steps for domain binding still involve DNS.

A Practical Suggestion​

When building a content site for the first time, the goal should be:

Get the site online stably at minimum cost first, rather than pursuing the most complex architecture from the start.