Notes, essays, and experiments.

Building a Private-to-Static WordPress Workflow

A private WordPress editor and a static public site can provide a comfortable writing workflow without exposing the CMS to the internet.

Why separate editing from publishing?

The editing origin keeps drafts, media, accounts, and database access on the protected network. The generated artifact contains only files a public reader needs.

Purple grid crossed by bright lime guide lines.
A generated test image used to verify inline-media export.

The bounded publishing loop

  1. Write and preview privately.
  2. Generate a fresh static artifact.
  3. Validate links, assets, and secrets before deployment.
generate -> validate -> canary -> approve -> publish

This acceptance post is deliberately small, but it exercises headings, metadata, taxonomy, images, lists, code, feeds, archives, and URL rewriting.