Overview
Watch along — first rebuild, faster pages, then the laptop-to-host story.
Video library
Each lesson is a screen recording with voiceover, plus written notes so you can watch or skim. If you learn faster when someone else clicks Publish, this tab is for you.
Recordings are produced from the scripts in the website repo
(docs/tivlo-ssg-video-scripts/). Until a video is published, the
player on that page is a placeholder — the notes underneath are still
the real lesson.
Two ways to use Tivlo SSG
Same WordPress host — anonymous visitors get static HTML from this
install (X-Tivlo-Static: hit). That is the usual “my site feels
snappier” win. No extra host. No AWS required.
Local WordPress, static hosting — you edit on your computer, export
HTML, and upload wp-content/tivlo-static/ to any host that can serve
files. Media and CSS/JS go through CloudFront + S3 so WordPress does
not need to stay online. Your laptop can nap. The brochure cannot.
Getting Started
Getting Started — end-user walkthroughs in the WordPress admin. Watch these first if you have not run a Full Rebuild yet.
Install and first rebuild
Activate Tivlo Static Site and export the site for the first time.
Verify static serving
Logged-out check, X-Tivlo-Static, and files on disk.
Edit a post — visitors see it
Publish as usual; the queue rebuilds HTML in the background.
Tour the three admin tabs
Plugin Settings, Build Console, and CDN & Media Sync.
Performance
Performance — why a file from disk is faster than cooking PHP, then a Lighthouse comparison on a demo site. We do not invent scores. The recording shows whatever the demo actually measures.
Why static HTML is faster
Skip the PHP bootstrap for anonymous page views — what still stays dynamic.
Lighthouse before and after
Same demo URL, logged out: live WordPress vs X-Tivlo-Static hit.
Deploy
Deploy — run WordPress locally and put the public site on hosting that does not need PHP.
Local WordPress, static hosting
Public Base URL, Full Rebuild, upload tivlo-static/ to any static host.
Media and CSS on S3
Keep images and assets working when WordPress is offline.
Deep Dives
Deep Dives — when you are ready for “why did my category page stay old?” and friends.
Incremental rebuilds
Related routes, comments, theme and menu changes.
How static serving decides
Headers, cookies, query strings, and 404.html.
What to export
Post types, archives, path exclusions, WooCommerce pages.
Fix a failed rebuild
Plain permalinks, loopback timeouts, a stuck queue.
Multisite networks
Network activate, bootstrap, per-site folders.
CloudFront in front of live WordPress
CDN Scenario 1 — no S3, origin is your public site.
How is this guide?