Local WordPress, static hosting
Edit in local WordPress and publish HTML on hosting that does not run PHP.
Placeholder embed
Replace videoId and poster when the recording is published.
Production script: docs/tivlo-ssg-video-scripts/07-local-wordpress-static-host.md.
Keep the WordPress editor you like. Do not keep PHP on the public internet if you do not need it. The public site becomes a folder of HTML. You upload that folder. Tivlo does not upload it for you.
What this video covers
- WordPress only as the editor (Local, Docker, or staging)
- Public Base URL set to the public site (for example
https://www.example.com) - Full Rebuild writing files under
wp-content/tivlo-static/ - Uploading those files to any static host (S3, Netlify, nginx, object storage — Tivlo has no built-in deploy adapter)
- Why media and CSS still need S3 + CloudFront if WordPress is not on the public internet
Key takeaways
Generation always fetches this WordPress install. Public Base URL only
rewrites strings in the written HTML. The plugin does not push to
Netlify or Vercel for you — you copy the folder. Skip Public Base URL
and you will ship a beautiful site full of localhost links. We have
seen it. It is funny once.
Related reading
How is this guide?