WordPress Multisite
Network-activate Tivlo SSG and keep each site’s HTML in its own folder.
Placeholder embed
Replace videoId and poster when the recording is published.
Production script:
docs/tivlo-ssg-video-scripts/20-use-case-multisite.md.
Who this is for
Agencies and networks that run many sites on one WordPress install (subdirectory or subdomain). You want each site to export its own HTML without activating the plugin on every subsite by hand.
Multisite is not a third publishing model. Each site still picks same-origin serving, local-export, and/or CDN the same way a single site does. This guide is the network layer on top — the filing cabinet, not a new photocopier.
Tivlo Static Site is network-aware (Network: true).
What isolation looks like
| Concern | Behavior |
|---|---|
| Settings | Per blog (wp_X_options) |
| Queue | {blog_prefix}tivlo_ssg_queue |
| Cron | Per site |
| Output | wp-content/tivlo-static/{site-slug}/ |
| Asset URL | {network_origin}/wp-content/tivlo-static/{site-slug}/ — not under the blog path |
| Public Base URL | Per site, when that site’s HTML is on another host |
| Content hooks | Run in the blog that changed |
Folder slug: Export Folder Slug in site settings, otherwise the
subdirectory path (/tivlo-dental/ → tivlo-dental), subdomain label, or
main for the primary site.
wp-content/tivlo-static/
main/
tivlo-dental/
another-site/One dentist cannot overwrite another dentist. That remains a feature.
The setup
Network Admin → Plugins → Network Activate Tivlo Static Site.
Network Admin → Settings → Tivlo Static Site. Click Bootstrap all sites (tables, cron, folders). Bootstrap does not export HTML. Housekeeping first, photocopies second.
Decide whether site admins may change Tivlo settings. If you lock
overrides, rebuild and queue actions stay available to site admins
with manage_options; saves show a denial banner.
Optionally enable automatic bootstrap when a new site is created.
Full rebuild — all enabled sites from the network screen (queues URLs; does not clear existing files), or rebuild one site from that site’s Build Console. Clearing files is site-only.
For a subsite whose HTML is hosted elsewhere, set that site’s Public Base URL, save, then Full Rebuild that site and deploy that slug’s folder.
Daily routine
Editors work in their own site admin and publish as usual. Incremental rebuilds stay in that blog. Network admins watch the sites table (file count, queue, output path) and use Process all site queues now when a quiet network is not hitting cron.
When this is the wrong guide
A single site does not need network activation. Use Faster pages on WordPress hosting (or the local-export pair) on a normal install.
Related reading
How is this guide?