Turn Your Bricks WordPress Site into a Static Site (Safer + Faster)

An in-depth walkthrough of using Bricks Static to export WordPress sites built with Bricks as secure static sites. The video demonstrates ZIP and GitHub export workflows, GitHub token setup, handling warnings, and deployment options (e.g., Cloudflare). It focuses on reducing maintenance and security risks while retaining Bricks forms and search where needed.

– Shows the ZIP export flow: site checks, domain/origin configuration, export, log review, download and direct deployment options.
– Demonstrates the GitHub workflow: create a private repository, generate a fine-grained personal access token with content read/write, connect Bricks Static and push static builds for version control.
– Explains common findings and fixes: Google Fonts are embedded for GDPR, PHP-running code elements are flagged, and missing assets (like favicons) appear as 404s in the export log.
– Covers deployment choices and workflow: use ZIP for simple hosting (Cloudflare Pages or FTP) or push to GitHub to integrate with CDNs and retain release history.

Quotes:

Static exports copy Google Fonts so your site never calls Google — good for GDPR.

Turn off WordPress, make changes, push a new static build, then turn it off again — get extra security without losing flexibility.

Personal access tokens are shown only once — copy it or it’s gone.