Overview
Pick the publishing model that matches how you actually run WordPress.
Placeholder embed
Replace videoId and poster when the recording is published.
Production script:
docs/tivlo-ssg-video-scripts/15-use-cases-overview.md.
Tivlo SSG is a WordPress plugin (Tivlo Static Site) that exports published URLs as HTML and can serve those files to people who are not logged in. Use Cases is where you choose a publishing model — not a list of slogans. Each guide below is a complete setup that matches what the plugin actually does.
Tivlo does not ship Netlify, Vercel, or WP-CLI deploy buttons. It writes
files under wp-content/tivlo-static/. You serve them from this
WordPress install, or you copy them to any host that can serve static
files. Old-fashioned. Fine.
The two publishing models
Most people pick row one and never look back. Row two is for “WordPress lives on my laptop, the public site is just HTML.”
| Keep WordPress online | WordPress only for editing | |
|---|---|---|
| Where PHP runs | The public host | Your laptop or private staging |
| Anonymous HTML | Tivlo on this install (X-Tivlo-Static: hit) | Files you uploaded to a static host |
| Admin, forms, REST | Still this WordPress | Only while you have the CMS running |
| Media and CSS | This WordPress, optionally via CloudFront | S3 + CloudFront if WordPress is offline |
| Start here | Faster pages on WordPress hosting | Local WordPress, static hosting |
Choose a guide
Faster pages on WordPress hosting
Same origin: skip the PHP bootstrap for anonymous HTML. No extra host.
Local WordPress, static hosting
Edit locally, set Public Base URL, upload tivlo-static/ to any static host.
Live WordPress + CloudFront
WordPress stays public; CloudFront caches media from that origin (no S3).
Static export + S3
Companion to local editing: media and CSS/JS on S3 so the laptop can go offline.
WordPress Multisite
Network-activate, isolate output per site, optional public host per subsite.
What stays true in every workflow
- Pretty permalinks are required (Settings → Permalinks — not Plain).
- Generation fetches this WordPress over HTTP (
X-Tivlo-SSG). - Saving settings does not rewrite HTML already on disk — use Build Console → Full Rebuild.
- Logged-in editors skip static serving by default. Verify in a private window.
- WooCommerce cart, checkout, and account pages are never exported.
What this video covers
- The two publishing models and when to pick each
- Why CDN Scenario 1 and Scenario 2 are not interchangeable
- Where Multisite fits (network of sites, not a third publishing model)
How is this guide?