# Static Publisher Architecture

Static Publisher treats WordPress as the source and control plane, the external exporter as the execution engine, and AWS as the delivery runtime. Editors keep using normal WordPress workflows, while the plugin handles queueing, diagnostics, scheduler rules, and runtime state. The separately installed exporter performs rendered-site crawling, asset discovery, URL rewriting, S3 deployment, and CloudFront invalidation.

This architecture is stronger than a simple in-process export button because the heavy work runs outside PHP. Queue jobs can be processed on the same host, on a dedicated runner, or in CI/CD, and the deployment environment can hold its own Playwright setup and AWS credentials.

Static Publisher also fits into the wider WP Suite stack. Gatey can handle Cognito login for statically delivered experiences, Static Guardian can protect CloudFront paths, AI-Kit can add grounded chat or AI features on top of a static site, and Flow can keep forms and workflows connected to backend services even when public pages are delivered from S3 + CloudFront.