Static export

Static export produces ordinary HTML, local assets, media, feeds, and supported plugin output that can be served without PHP. The result is public publishing output, not an editable tinymash installation and not a backup.

Drafts, private author spaces, admin routes, users, configuration, revisions, private plugin state, and runtime files are not exported.

Administration

Authors can export their own public author space from Profile > Static export. A superadmin can export the public site from System > Static export and exclude selected public author spaces.

Generated administration archives are private, permission-checked, and retained for a limited time. Download or remove them when finished.

CLI

Create managed export artifacts:

php8.4 bin/tinymash.php static-export:author cajo
php8.4 bin/tinymash.php static-export:site

Write directly to a new or empty directory:

php8.4 bin/tinymash.php static-export:site \
  --base-url=https://example.com --output=/path/to/public-output

Use --exclude-author=<slug> more than once to omit author spaces from a site export. An explicit output directory must be new or empty; tinymash will not merge a fresh export over stale files.

Dynamic features

A static host cannot run forms, sessions, authentication, remote refreshes, queues, cron, or PHP-backed search. Plugins declare whether their public output is static, a snapshot, a placeholder, omitted, or supported through local JavaScript and exported data.

Review export-report.json before publishing. It records exported routes and assets, plugin modes, warnings, and internal URLs that still point to the live site.

The export base URL must match the final public URL, including any sub-URL. Test navigation, images, feeds, search, pagination, canonical URLs, and representative desktop and mobile pages on the actual static host.