Jessy Huang
Back to writing

Portable public sites are worth the extra boundary

Building the public face of a project as source content first, then static output, keeps publishing simple.

Static sitesDeploymentGitHub Pages

I like a public site that can move between hosts without needing a rewrite.

That usually means:

  • source content lives in one repo,
  • the build step is deterministic,
  • the deploy target is just an output destination.

This is not an aesthetic preference. It is operational discipline. If the source repository can be rebuilt locally and the output repo only receives files, the system is easier to audit and easier to repair.

What the boundary buys you

When the source site is separate from the output repo, publishing becomes a predictable handoff:

  1. write content,
  2. build static assets,
  3. publish the artifact.

The site stops depending on hidden state in the deploy target.

Why this feels calm

The reader sees content, not release machinery. The maintainer sees a short build path instead of a bespoke deployment ritual. That is enough.