First export
Your first Tivlo SSG export — about ten minutes, one private window.
This walkthrough assumes the plugin is already activated. If Settings → Tivlo Static Site is missing, start with Installation.
You are about to: fix permalinks (if needed), glance at the defaults, press Full Rebuild, wait for the to-do list to hit zero, then sneak into a private window like a visitor. That last bit is the whole trick.
Stay logged out to verify
With Skip static delivery for logged-in users on (the default),
you will not see X-Tivlo-Static: hit while you are logged into
wp-admin. Your admin bar is not a bug. Use a private window for the
last step — treat it as the visitor’s browser, because it is.
Open Settings → Permalinks. Choose Post name (or any structure other than Plain) and click Save Changes. Even if you already use Post name, clicking Save is cheap insurance — it flushes rewrite rules.
Open Settings → Tivlo Static Site.
On Plugin Settings, look at the defaults. For a typical blog or brochure site they are already what you want:
- Enable static generation — on
- Serve static HTML directly — on
- Skip static delivery for logged-in users — on
- Content types — Post, Page
- Site Pages — Front Page, Posts Page, Date Archives, Author Archives, 404 Page
You can leave every chip alone on day one. Curiosity is allowed later.
Click Save Settings if you changed anything. Saving does not reprint pages that already exist. First time around, there usually are none, so this is just “lock in the rules.”
Switch to the Build Console tab and click Full Rebuild. Optionally enable Clear existing static files before running a full rebuild if you want a clean first export (useful if you already clicked around).
Wait until Queue Pending Tasks is 0. On a local or quiet site,
WP-Cron may be napping. Click Process Queue Now a few times
until the queue drains. Keep the Build tab open — watching the log
is oddly satisfying, like a progress bar you are allowed to stare
at.
Open a published page in a private window. In DevTools → Network, click the document request (the HTML, not an image) and look at Response Headers:
X-Tivlo-Static: hitThat sticker means Tivlo served the file, not a full PHP cook.
What you should see on disk
Same idea as permalinks: the public URL becomes a folder.
| Public URL | File |
|---|---|
/ | wp-content/tivlo-static/index.html |
/about/ | wp-content/tivlo-static/about/index.html |
You do not have to open those files. They are there so Tivlo (or a static host) can read them.
How is this guide?