
外掛標籤
開發者團隊
② 後台搜尋「Glaciate – Static Site Publisher」→ 直接安裝(推薦)
原文外掛簡介
Glaciate turns your WordPress site into plain HTML, CSS and images that any web host can serve, without PHP or a database. You keep writing in WordPress; visitors get a static copy that is fast, cheap to host and hard to break.
Works with your theme and plugins. Pages are rendered by your own site, exactly as a visitor sees them, so block themes, classic themes and page builders all work.
Only what changed is rebuilt. While a page renders, Glaciate records which posts, terms, authors and settings it used. Edit a post, and only the pages that show it are rebuilt and redeployed.
One choice to get started. Activate, pick where the static site goes, and publish.
Publishes where you host. A folder on your server, a ZIP file, Amazon S3 or any S3-compatible storage (with CloudFront invalidation), another server over SFTP, a Git repository for GitHub Pages, GitLab Pages and similar hosts, Netlify, or Cloudflare. Each target is configured on the settings screen or from WP-CLI, and credentials are stored encrypted and never shown again.
Publishes when you want. Right after you save, at set times of day, or only when you click Publish. A full rebuild runs nightly (or weekly, or never) at a time you choose.
Forms keep working. Contact Form 7, WPForms, Gravity Forms and comment forms on the static site send their submissions back to WordPress, where the form plugin handles them as usual. WordPress can receive them itself, or a small receiver you put on any PHP host, Cloudflare or Netlify can pass them on, so WordPress can stay private. Spam is held off with a hidden field, a minimum time on the page and a limit per visitor, plus an optional captcha.
Search keeps working. Your search forms search the static copy in the visitor’s browser, using an index published with the site. No server, no outside service.
Feels like WordPress. A “Publish to static” button in the editor, a status in the admin bar, a Site Health check, and a WP-CLI command for everything.
No upsells. There is no premium version, no license key and no tracking. The plugin contacts no outside service except the deploy target you choose.
Links, images, srcset, stylesheets, scripts, structured data, feeds and sitemaps are all rewritten to your public address. A 404 page, a _redirects file and a _headers file (so feeds keep their type on Netlify and Cloudflare) are generated for you.
For developers
Every stage has actions and filters (list of hooks), and deploy targets are pluggable through a small interface. All features are available from WP-CLI: wp glaciate build, status, why, deploy, zip, settings, target, secret, schedule, forms, doctor and more.
Privacy
The plugin doesn’t collect or store personal data of its own. It contacts no outside service on its own: the only remote requests go to deploy targets you configure (Amazon S3 or another S3-compatible service, CloudFront, an SFTP server, a Git repository, Netlify, or Cloudflare), and they carry your built site and the credentials you entered for that target.
When you turn on Forms, what visitors type into forms on the static site, with their IP address and browser name, is sent to the receiver you chose and handed to the form plugin, which may email or store it as it does on your site. Glaciate itself keeps only a hashed IP address for ten minutes, for its rate limit. If you set up a webhook, a copy of each submission goes there. If you choose a captcha, visitors’ browsers load it from Cloudflare (Turnstile) or hCaptcha on pages with forms, and each answer is checked with that provider along with the visitor’s IP address. Mention these in your site’s privacy policy.
External services
Glaciate contacts no outside service on its own. Each service below is used only when you choose it in Settings, and only for what is described.
Amazon S3 and CloudFront (Amazon Web Services), when the deploy target is Amazon S3 or an S3-compatible service. Each deploy lists the bucket and sends the built site’s files to the S3 endpoint of the bucket’s region (s3.
Git hosting (for example GitHub), when the deploy target is Git. Each deploy reads the branch Glaciate publishes to and pushes the built site to it, with the token you entered, at the repository address you entered. For GitHub: terms, privacy statement.
Netlify, when the deploy target is Netlify. Each deploy sends the list of the built site’s files and their hashes, then the files Netlify doesn’t have yet, to api.netlify.com with the access token you entered. Terms, privacy policy.
Cloudflare, when the deploy target is Cloudflare. Each deploy sends the built site’s file list and changed files to the Workers API (api.cloudflare.com) of the account you entered, with your API token. Terms, privacy policy.
Cloudflare Turnstile, when you choose it as the form captcha. Visitors’ browsers load its script from challenges.cloudflare.com on static pages with forms; each form answer is sent there for checking (challenges.cloudflare.com/turnstile/v0/siteverify), with the visitor’s IP address, when the form is submitted. Terms, Turnstile privacy policy.
hCaptcha, when you choose it as the form captcha. Visitors’ browsers load its script from js.hcaptcha.com on static pages with forms; each form answer is sent to hCaptcha for checking (api.hcaptcha.com/siteverify), with the visitor’s IP address, when the form is submitted. Terms, privacy policy.
A webhook address or SFTP server you enter receives what is described in Settings next to it; those are your own services.
Third-party libraries
Action Scheduler by Automattic (GPL-3.0-or-later), used to run builds in the background.
phpseclib (MIT), with paragonie/constant_time_encoding and paragonie/random_compat (MIT), used for SFTP deploys. They are bundled under the Glaciate\Vendor namespace, so another plugin’s copy of phpseclib can’t replace them.
