Quick Start
Welcome — what Tivlo SSG does, in plain WordPress language.
Welcome — you already know WordPress
If you can publish a page, you can use Tivlo SSG. The plugin’s real name in WordPress is Tivlo Static Site. “SSG” just means static site generator: it takes the published pages you already have and saves them as ordinary HTML files.
Think of it like this. WordPress is the kitchen. Every time a visitor
asks for /about/, the kitchen normally cooks that page from scratch
(PHP, plugins, theme, database). Tivlo makes a plated copy ahead of time
and serves that to guests. You stay in the kitchen while you edit.
Guests get the plate.
Logged-in editors keep seeing live WordPress by default, so the admin, the block editor, and previews still behave the way you expect.
Use the switcher at the top of the sidebar to move between User Guide, Academy, Use Cases, and Changelog.
Tivlo SSG 1.0.0 is the first public release — peek at the changelog if you like knowing what shipped.
[IMAGE: hero-screenshot]
Full-width annotated screenshot of the Tivlo SSG admin (sidebar + Build Console with status cards, progress bar, and log panel).
Caption: “Tivlo SSG admin — three tabs for settings, builds, and CDN.”
Installation
Activate Tivlo Static Site. WordPress creates the export folder, queue, and cron for you.
First export
About ten minutes: permalinks, Full Rebuild, then a private-window check.
Build Console
The “go” tab — rebuild, queue, logs, and a big red “clear everything” if you need it.
CDN & Media Sync
Optional. Speed up images with CloudFront, or copy media to S3.
Academy
Sit with a coffee and watch: first rebuild, Lighthouse, local WordPress to static hosting.
Use Cases
Same host, faster pages — or edit on your laptop and ship HTML.
What you get
- When you publish or update a post, Tivlo rebuilds that page (and the lists it belongs on) instead of the entire site
- Anonymous visitors can receive a file from disk, confirmed by the
response header
X-Tivlo-Static: hit - A background queue (WP-Cron) does the work — or you click Process Queue Now when you are impatient, which is often, and that’s fine
- Multisite gets a folder per site under
wp-content/tivlo-static/{site-slug}/ - Optional CloudFront rewriting and Amazon S3 sync for media and assets
- On export, Tivlo can keep CSS/JS as real files and tidy the HTML
The four beats (no developer hat required)
Export — Tivlo walks your public URLs (posts, pages, archives —
whatever you tick) and writes one index.html per path under
wp-content/tivlo-static/. /about/ becomes
wp-content/tivlo-static/about/index.html. Same idea as a folder of
pages, not a mystery cache.
Queue — A content change adds that URL to a to-do list. If related
rebuilds are on, home, archives, and categories get on the list too.
Jobs live in a database table named {prefix}tivlo_ssg_queue. You
never have to open that table unless something is stuck.
Generate — For each job, WordPress visits its own public URL
(like a guest would) and saves what it sees. That visit includes an
X-Tivlo-SSG header so Tivlo does not accidentally serve an old file
to itself. Theme, blocks, and plugins all show up in the snapshot.
Serve — When a logged-out visitor asks for a page and a matching file exists, Tivlo hands it over and WordPress can stop cooking. Admin, REST, AJAX, forms, logged-in sessions, and WooCommerce cart / checkout / account still go through live WordPress. Shopping carts are not photocopies — they are personal, and Tivlo leaves them alone.
No phone-home
Generation, serving, and the little banners on the settings screen use this WordPress site and files that shipped with the plugin. Tivlo does not call home, and it does not fetch a remote promo feed. Your site stays your site.
How is this guide?