Evolution of Static Sites

Why “Islands Architecture” is Changing the Web in 2026#

The Shift in Strategy#

For many years WordPress set the bar: easy installs, editorial workflows, and server-rendered pages that worked out of the box for blogs and small sites. That period (the “WordPress era”) taught us the value of simple publishing and immediate functionality.

Later came the SSG era (Hugo and similar): performance from pre-built HTML and tiny hosting footprints.

Now we’re in a third phase where frameworks (Next.js, Docusaurus, Astro) balance server rendering, partial hydration, and selective client-side interactivity. The key question today is when and where JavaScript runs (hydration), not just whether a site is SSG or SSR.

Github Pages

Static content hosting with GitHub Pages#

Let’s review the nuances between site types and how to automate their deployment.

GitHub Pages Site Types#

FeatureUser SiteOrganization SiteProject Site
Primary IntentPersonal portfolio, resume, or central hub.Brand, company, or collective identity.Documentation or landing page for a specific repo.
Repo Namingusername.github.ioorgname.github.ioany-repo-name
Default URLhttps://username.github.iohttps://orgname.github.iohttps://username.github.io/repo/
Apex DomainSupported (e.g., domain.com).Supported (e.g., company.com).Supported (e.g., project.com).
SubdomainSupported (e.g., user.domain.com).Supported (e.g., org.domain.com).Supported (e.g., docs.domain.com).
CapacityOne (1) per account.One (1) per organization.Unlimited per account/org.
PermissionsIndividual ownership.Shared team administrative access.Inherited from the project repository.

Deployment Workflow Strategies#

Static site generators (SSGs) like Hugo or MkDocs require a build step to turn source files into HTML. How you handle that build defines your workflow.